[prev in list] [next in list] [prev in thread] [next in thread]
List: dm-devel
Subject: Re: [dm-devel] multipath - AAArgh! How do I turn
From: John Hughes <john () Calva ! COM>
Date: 2009-09-30 17:11:10
Message-ID: 4AC3912E.3060908 () Calva ! COM
[Download RAW message or body]
Moger, Babu wrote:
> You will see "features=1 queue_if_no_path" if you have one of the following entry \
> in your multipath.conf.
> 1. Features "1 queue_if_no_path"
>
> Or
>
> 2. no_path_retry 5
>
Ah, that was the problem. Now I have "features=0".
I did my silly test again (deleting a LUN that was in use from the
external cabinet) and the system kept working. The errors on the dm-xxx
device propogated back to mdadm which marked it as failed an all was well.
Except that I'm still getting lots of I/O errors:
[ 9019.822396] Buffer I/O error on device dm-17, logical block 17790463
[ 9019.822432] Buffer I/O error on device dm-17, logical block 0
[ 9019.822473] Buffer I/O error on device dm-17, logical block 0
[ 9020.735190] sd 4:0:0:1: queueing MODE_SELECT command.
[ 9020.771075] sd 4:0:0:1: MODE_SELECT failed with sense 0x59100.
[ 9020.793828] sd 4:0:0:1: [sdah] Result: hostbyte=DID_OK \
driverbyte=DRIVER_SENSE,SUGGEST_OK [ 9020.793894] sd 4:0:0:1: [sdah] Sense Key : \
Illegal Request [current] [ 9020.793932] sd 4:0:0:1: [sdah] Add. Sense: Logical unit \
not supported [ 9020.793968] end_request: I/O error, dev sdah, sector 0
[ 9020.793995] device-mapper: multipath: Failing path 66:16.
... endlessly repeating
I was able to stop the errors by
1. removing the failed multipath from the mdadm array
2. using the multipath -f command to flush the deleted disk.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic