On May 16, 10:41 pm, Konrad Rzeszutek <[EMAIL PROTECTED]> wrote: > > So the block disks show up fine. That means iSCSI works just fine. >
starting multipath up solved the problem > You only see one disk? Either way, are you running multipath on your machine? > If you are, what is the multipath -ll output? Anyway, I am sending the multipath output in the configuration that works # multipath -ll 3600508b300920350a640cb720bce000edm-0 COMPAQ,MSA1000 VOLUME [size=838G][features=1 queue_if_no_path][hwhandler=1 hp_sw] \_ round-robin 0 [prio=4][active] \_ 13:0:0:1 sdb 8:16 [active][ready] Sometimes, depending mainly on the path_checker setting, the device fails. Once I had a segfault in multipathd. May 17 19:41:40 <hostname> multipathd: sdb: tur checker reports path is down May 17 19:41:51 <hostname> multipathd: sdb: tur checker reports path is down May 17 19:42:01 <hostname> multipathd: sdb: tur checker reports path is down May 17 19:42:07 <hostname> multipathd: 3600508b3009203503b2fc2c200040011: stop event checker thread May 17 19:42:07 <hostname> kernel: multipathd[13092]: segfault at 0000000000000012 rip 00002b0b549d541d rsp 00007fff5682d1b0 error 4 May 17 19:42:07 <hostname> multipathd: error calling out /sbin/scsi_id -g -u -s /block /sda May 17 19:42:07 <hostname> multipathd: sdb: checker msg is "readsector0 checker reports path is down" May 17 19:42:07 <hostname> multipathd: 3600508b3009203503b2fc2c200040011: event checker started In the present configuration the device sometimes goes away but returns quickly May 18 17:52:14 <hostname> kernel: sd 13:0:0:1: Device not ready: <6>: Current: sense key: Not Ready May 18 17:52:14 <hostname> kernel: Additional sense: Logical unit not ready, cause not reportable May 18 17:52:14 <hostname> kernel: end_request: I/O error, dev sdb, sector 4775 May 18 17:52:14 <hostname> kernel: device-mapper: dm-multipath: Failing path 8:16. May 18 17:52:14 <hostname> multipathd: 8:16: mark as failed May 18 17:52:14 <hostname> multipathd: 3600508b300920350a640cb720bce000e: remaining active paths: 0 May 18 17:52:19 <hostname> multipathd: sdb: hp_sw checker reports path is ghost May 18 17:52:19 <hostname> kernel: device-mapper: hp-sw: Flushing I/O May 18 17:52:19 <hostname> kernel: device-mapper: hp-sw: sending START_STOP_UNIT command May 18 17:52:19 <hostname> multipathd: 8:16: reinstated May 18 17:52:19 <hostname> multipathd: 3600508b300920350a640cb720bce000e: remaining active paths: 1 > The next step for enterprise storages, such as the HP StorageWorks > is to issue a START SCSI command - which is what you should see if you > are using multipath. The path checker would start the LUN. Yes that was the original problem. There was no multipath running and HP StorageWorks array would not start. When multipath was started the problem went away. Thank you for the advice. I have multipath 0.4.7 running the default configuration (no /etc/ multipath.conf) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---
