search

TritonDataCenter / smartos-live

For more information, please see http://smartos.org/ For any questions that aren't answered there, please join the SmartOS discussion list: https://smartos.topicbox.com/groups/smartos-discuss
1.58k stars 249 forks source link

failed to use iSCSI target on same host #683

Open haiwanglaile opened 8 years ago

haiwanglaile commented 8 years ago

I created one iscsi target on my server 10.20.2.30, then tried to create zpool on this target, failed! zfs_ create -b 4k -V 40g dzp1/localiscsi40g svcadm enable stmf stmfadm create-lu -p blk=4096 -p guid=600144F04E086D08000058255D130003 /dev/zvol/rdsk/dzp1/localiscsi40g stmfadm add-view 600144F04E086D08000058255D130003 svcadm enable -r svc:/network/iscsi/target:default itadm create-target iscsiadm modify discovery -t enable iscsiadm add discovery-address 127.0.0.1 devfsadm -i iscsi zpool create iscsipool c2t600144F04E086D08000058255D130003d0

failed to create zpool and output like below cannot create 'iscsipool': one or more devices is currently unavailable

get message from /var/adm/message like below

2016-11-22T03:35:41.362053+00:00 40-8d-5c-13-9c-8b genunix: [ID 483743 kern.info] /scsi_vhci/disk@g600144f04e086d08000058255d130003 (sd5) multipath status: degraded: path 1 iscsi0/disk@0000iqn.2010-08.org.illumos:02:39468604-a6cb-6326-a019-d5033d2042390001,0 is online 2016-11-22T03:37:19.356128+00:00 40-8d-5c-13-9c-8b scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):#012#011/scsi_vhci/disk@g600144f04e086d08000058255d130003 (sd5): Command Timeout on path iscsi0/disk@0000iqn.2010-08.org.illumos:02:39468604-a6cb-6326-a019-d5033d2042390001,0 2016-11-22T03:38:20.358390+00:00 40-8d-5c-13-9c-8b iscsi: [ID 431120 kern.warning] WARNING: iscsi connection(7/3f) closing connection - target requested reason:0x7 2016-11-22T03:38:20.359448+00:00 40-8d-5c-13-9c-8b scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1 2016-11-22T03:38:20.359453+00:00 40-8d-5c-13-9c-8b iscsi: [ID 732673 kern.info] NOTICE: iscsi session(6) iqn.2010-08.org.illumos:02:39468604-a6cb-6326-a019-d5033d204239 offline#012 2016-11-22T03:38:20.359466+00:00 40-8d-5c-13-9c-8b scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1 2016-11-22T03:38:20.359468+00:00 40-8d-5c-13-9c-8b scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x0 2016-11-22T03:38:20.359479+00:00 40-8d-5c-13-9c-8b scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1 2016-11-22T03:38:20.359481+00:00 40-8d-5c-13-9c-8b scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x0 2016-11-22T03:38:20.359494+00:00 40-8d-5c-13-9c-8b scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1 2016-11-22T03:38:20.359506+00:00 40-8d-5c-13-9c-8b scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x0 2016-11-22T03:38:20.359584+00:00 40-8d-5c-13-9c-8b scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1 2016-11-22T03:38:20.359588+00:00 40-8d-5c-13-9c-8b scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x0 2016-11-22T03:38:20.459617+00:00 40-8d-5c-13-9c-8b scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g600144f04e086d08000058255d130003 (sd5):#012#011SYNCHRONIZE CACHE command failed (5)#012 2016-11-22T03:38:20.459654+00:00 40-8d-5c-13-9c-8b scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g600144f04e086d08000058255d130003 (sd5):#012#011Unable to clean up memory because of pending I/O#012 2016-11-22T03:38:21.486622+00:00 40-8d-5c-13-9c-8b iscsi: [ID 559844 kern.info] NOTICE: iscsi session(6) iqn.2010-08.org.illumos:02:39468604-a6cb-6326-a019-d5033d204239 online#012 2016-11-22T03:40:23.348572+00:00 40-8d-5c-13-9c-8b genunix: [ID 483743 kern.info] /scsi_vhci/disk@g600144f04e086d08000058255d130003 (sd5) multipath status: failed: path 1 iscsi0/disk@0000iqn.2010-08.org.illumos:02:39468604-a6cb-6326-a019-d5033d2042390001,0 is offline

rmustacc commented 7 years ago

Hi, iscsi isn't something that we use at Joyent at all, so I'm afraid you'll need to dig in a bit more and understand why it's failing. I'm not sure if this is generally supported or not, the broader illumos community may know better.