Q: multipath not recovering after device was offline
Hi!
This is not an exact open-iscsi question, but tighlty related:
On a SAN using FibreChannel I had a 4-way multipath device. The basic
configuration (without aliases for devices) is:
devices {
device {
vendor HP
product HSV2.*
path_grouping_policy group_by_prio
path_checker tur
prio alua
failback immediate
#polling_interval 30
no_path_retry 1000
features 1 queue_if_no_path
}
}
I did a LUN shrink on the storage system (because I had created the LUN too
large by mistake). During that the LUN went offline, and multipath did detect
that fine. However after the LUN shrink was complete (and the LUN was supposed
to be online again), multipath still blocked any access to the device (like
fdisk -l). Reboot did fix it, but I'm hoping for a better solution.
I'm asking theis question here, because I expect that with iSCSI the problem
would have been much the same.
So:
1) Did I misconfigure multipath?
2) Could I do something to make multipath rediscover the online-again paths?
Lengthy Syslog messages (only a part):
May 11 16:07:06 hostname multipathd: 65:224: mark as failed
May 11 16:07:06 hostname multipathd: DISK-E1: remaining active paths: 3
May 11 16:07:06 hostname kernel: [ 8064.784883] sd 3:0:2:4: [sdae] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 16:07:06 hostname kernel: [ 8064.784889] sd 3:0:2:4: [sdae] Sense Key :
Illegal Request [current]
May 11 16:07:06 hostname kernel: [ 8064.784894] sd 3:0:2:4: [sdae] Add. Sense:
Logical block address out of range
May 11 16:07:06 hostname kernel: [ 8064.784899] sd 3:0:2:4: [sdae] CDB:
Read(10): 28 00 3e 7f ff f8 00 00 08 00
May 11 16:07:06 hostname kernel: [ 8064.784906] end_request: I/O error, dev
sdae, sector 1048575992
May 11 16:07:06 hostname kernel: [ 8064.784911] device-mapper: multipath:
Failing path 65:224.
May 11 16:07:06 hostname kernel: [ 8064.787969] sd 2:0:0:4: [sdac] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 16:07:06 hostname kernel: [ 8064.787973] sd 2:0:0:4: [sdac] Sense Key :
Illegal Request [current]
May 11 16:07:06 hostname kernel: [ 8064.787976] sd 2:0:0:4: [sdac] Add. Sense:
Logical block address out of range
May 11 16:07:06 hostname kernel: [ 8064.787980] sd 2:0:0:4: [sdac] CDB:
Read(10): 28 00 3e 7f ff f8 00 00 08 00
May 11 16:07:06 hostname kernel: [ 8064.787987] end_request: I/O error, dev
sdac, sector 1048575992
May 11 16:07:06 hostname kernel: [ 8064.787992] device-mapper: multipath:
Failing path 65:192.
May 11 16:07:06 hostname kernel: [ 8064.792011] sd 2:0:3:4: [sdad] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 16:07:06 hostname kernel: [ 8064.792015] sd 2:0:3:4: [sdad] Sense Key :
Illegal Request [current]
May 11 16:07:06 hostname kernel: [ 8064.792019] sd 2:0:3:4: [sdad] Add. Sense:
Logical block address out of range
May 11 16:07:06 hostname kernel: [ 8064.792023] sd 2:0:3:4: [sdad] CDB:
Read(10): 28 00 3e 7f ff f8 00 00 08 00
May 11 16:07:06 hostname kernel: [ 8064.792031] end_request: I/O error, dev
sdad, sector 1048575992
May 11 16:07:06 hostname kernel: [ 8064.792037] device-mapper: multipath:
Failing path 65:208.
May 11 16:07:06 hostname kernel: [ 8064.793499] sd 3:0:3:4: [sdaf] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 16:07:06 hostname kernel: [ 8064.793502] sd 3:0:3:4: [sdaf] Sense Key :
Illegal Request [current]
May 11 16:07:06 hostname kernel: [ 8064.793506] sd 3:0:3:4: [sdaf] Add. Sense:
Logical block address out of range
May 11 16:07:06 hostname kernel: [ 8064.793509] sd 3:0:3:4: [sdaf] CDB:
Read(10): 28 00 3e 7f ff f8 00 00 08 00
May 11 16:07:06 hostname kernel: [ 8064.793519] end_request: I/O error, dev
sdaf, sector 1048575992
May 11 16:07:06 hostname kernel: [ 8064.793524] sd 3:0:3:4: [sdaf] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 16:07:06 hostname kernel: [ 8064.793529] device-mapper: multipath:
Failing path 65:240.
May 11 16:07:06 hostname kernel: [ 8064.793536] sd 3:0:3:4: [sdaf] Sense Key :
Illegal Request [current]
May 11 16:07:06 hostname kernel: [ 8064.793541] sd 3:0:3:4: [sdaf] Add. Sense:
Logical block address out of range
May 11 16:07:06 hostname kernel: [ 8064.793545] sd 3:0:3:4: [sdaf] CDB:
Read(10): 28 00 3e 7f ff 80 00 00 08 00
May 11 16:07:06 hostname kernel: [ 8064.793553] end_request: I/O error, dev
sdaf, sector 1048575872
May 11 16:07:07 hostname multipathd: 65:192: mark as failed
May 11 16:07:07 hostname multipathd: DISK-E1: remaining active paths: 2
May 11 16:07:07 hostname multipathd: 65:208: mark as failed
May 11 16:07:07 hostname multipathd: DISK-E1: remaining active paths: 1
May 11 16:07:07 hostname multipathd: 65:240: mark as failed
May 11 16:07:07 hostname multipathd: DISK-E1: Entering recovery mode:
max_retries=1000
May 11 16:07:07 hostname multipathd: DISK-E1: remaining active paths: 0
May 11 16:07:07 hostname multipathd: DISK-E1:
Re: Q: multipath not recovering after device was offline
On 05/12/2011 01:30 AM, Ulrich Windl wrote:
Hi!
This is not an exact open-iscsi question, but tighlty related:
On a SAN using FibreChannel I had a 4-way multipath device. The basic
configuration (without aliases for devices) is:
devices {
device {
vendor HP
product HSV2.*
path_grouping_policy group_by_prio
path_checker tur
prio alua
failback immediate
#polling_interval 30
no_path_retry 1000
features 1 queue_if_no_path
}
}
I did a LUN shrink on the storage system (because I had created the LUN too
large by mistake). During that the LUN went offline, and multipath did detect that fine.
However after the LUN shrink was complete (and the LUN was supposed to be online again),
multipath still blocked any access to the device (like fdisk -l). Reboot did fix it, but
I'm hoping for a better solution.
I'm asking theis question here, because I expect that with iSCSI the problem
would have been much the same.
So:
1) Did I misconfigure multipath?
2) Could I do something to make multipath rediscover the online-again paths?
I think you need to rescan the devices at the scsi layer level (like
doing a echo 1 /sys/block/sdX/device/rescan) then run some multipath
to command, then run some FS and LVM commands if needed.
Here is some info for the multipath command from red hat
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch21s14s03.html
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-iscsi@googlegroups.com.
To unsubscribe from this group, send email to
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
Changes made on iSCSI disk are not shown on initiator
Hello, the problem I am having is, that luckily I was able to correctly set- up the whole iSCSI-environment, the disk is successfully mounted on my initiator and everything seemed to be as expected. However, when I now copy a file from the initiator to the target (via the mounted folder) I can see this file afterwards only on the initiator, but not on the target. Means, I open a Terminal on the target and take a look what is available on the disk, but unfortunately the disk is still shown as empty, despite showing the file being there via the Initiator. While copying I took a look in Wireshark and it was shown that the transfer really is happening, but the file still isn't there!! What could be the problem? Is it maybe because my shared disk is formatted with ext3? This shouldn't be the problem however, since the tutorial found under ( http://www.howtoforge.com/using-iscsi-on-ubuntu-9.04-initiator-and-target ) also suggested this file system. Thanks! -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Changes made on iSCSI disk are not shown on initiator
On 2011. May 12. 13:10:10 Adnan Pasic wrote: the problem I am having is, that luckily I was able to correctly set- up the whole iSCSI-environment, the disk is successfully mounted on my initiator and everything seemed to be as expected. However, when I now copy a file from the initiator to the target (via the mounted folder) I can see this file afterwards only on the initiator, but not on the target. Are you trying to say that you mounted the same device that you're exporting via iSCSI, on the target machine as well? This is quite a bad idea, and very likely leads to data corruption as you experienced. Ext3 is not a cluster file system, it should be mounted only by one machine at a time. I repeat: *do not do this*, it will not work. If you absolutely need something like this, use a clustered file system like OCFS2 on the raw device. Cheers, -- cc -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Antw: Changes made on iSCSI disk are not shown on initiator
Ouch! You are doing disk sharing via iSCSI, and you are using a non-cluster filesystem? Ouch! Lucky that the pieces are not flying around your head already (i.e. kernel panic, data corruption) Regards, Ulrich Adnan Pasic pq...@yahoo.de schrieb am 12.05.2011 um 13:10 in Nachricht 0cccb82e-bdf5-483a-b6ff-0145b3f35...@gv8g2000vbb.googlegroups.com: Hello, the problem I am having is, that luckily I was able to correctly set- up the whole iSCSI-environment, the disk is successfully mounted on my initiator and everything seemed to be as expected. However, when I now copy a file from the initiator to the target (via the mounted folder) I can see this file afterwards only on the initiator, but not on the target. Means, I open a Terminal on the target and take a look what is available on the disk, but unfortunately the disk is still shown as empty, despite showing the file being there via the Initiator. While copying I took a look in Wireshark and it was shown that the transfer really is happening, but the file still isn't there!! What could be the problem? Is it maybe because my shared disk is formatted with ext3? This shouldn't be the problem however, since the tutorial found under ( http://www.howtoforge.com/using-iscsi-on-ubuntu-9.04-initiator-and-target ) also suggested this file system. Thanks! -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Changes made on iSCSI disk are not shown on initiator
the mounted folder) I can see this file afterwards only on the initiator, but not on the target. Means, I open a Terminal on the The basic rule is that if you are going to export storage to a single machine, use iSCSI. If you need shared storage, use NFS instead. You could consider a shared storage file system like Oracle's ASM, but they aren't so easy to deal with. NFS4 has locking, user authentication, and everything you need built into the protocol. Mark -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
