Hi All, I have read various threads here (and, yes, the documentation) trying to find out how to properly reconfigure the list of LUNs known to Solaris when LUNs are removed/added on the iSCSI target (Netapp in my case).
http://www.opensolaris.org/jive/thread.jspa?messageID=235052 suggests to use devfsadm -C, other documents suggest devfsadm -i iscsi, but none of them works (at least not for the removal case): # iscsiadm list target -S iqn.1992-08.com.netapp:sn.135019344 Target: iqn.1992-08.com.netapp:sn.135019344 Alias: - TPGT: 1001 ISID: 4000002a0000 Connections: 0 Target: iqn.1992-08.com.netapp:sn.135019344 Alias: moonglow TPGT: 2000 ISID: 4000002a0000 Connections: 1 LUN: 6 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t8d0s2 LUN: 5 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t7d0s2 LUN: 4 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t6d0s2 LUN: 3 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t5d0s2 LUN: 2 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t4d0s2 LUN: 1 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t2d0s2 LUN: 0 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t19d0s2 # devfsadm -Cv [...] devfsadm[14109]: verbose: removing file: /dev/rdsk/c2t8d0s6 devfsadm[14109]: verbose: removing file: /dev/rdsk/c2t8d0s7 # iscsiadm list target -S iqn.1992-08.com.netapp:sn.135019344 Target: iqn.1992-08.com.netapp:sn.135019344 Alias: - TPGT: 1001 ISID: 4000002a0000 Connections: 0 Target: iqn.1992-08.com.netapp:sn.135019344 Alias: moonglow TPGT: 2000 ISID: 4000002a0000 Connections: 1 LUN: 6 Vendor: NETAPP Product: LUN OS Device Name: LUN: 5 Vendor: NETAPP Product: LUN OS Device Name: LUN: 4 Vendor: NETAPP Product: LUN OS Device Name: LUN: 3 Vendor: NETAPP Product: LUN OS Device Name: LUN: 2 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t4d0s2 LUN: 1 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t2d0s2 LUN: 0 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t19d0s2 -> Note: This has removed the devices, but not the LUNs # devfsadm -i iscsi # iscsiadm list target -S iqn.1992-08.com.netapp:sn.135019344 Target: iqn.1992-08.com.netapp:sn.135019344 Alias: - TPGT: 1001 ISID: 4000002a0000 Connections: 0 Target: iqn.1992-08.com.netapp:sn.135019344 Alias: moonglow TPGT: 2000 ISID: 4000002a0000 Connections: 1 LUN: 6 Vendor: NETAPP Product: LUN OS Device Name: LUN: 5 Vendor: NETAPP Product: LUN OS Device Name: LUN: 4 Vendor: NETAPP Product: LUN OS Device Name: LUN: 3 Vendor: NETAPP Product: LUN OS Device Name: LUN: 2 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t4d0s2 LUN: 1 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t2d0s2 LUN: 0 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t19d0s2 -> No change What *does* help is to disable/enable the discovery method (here: sendtargets): # iscsiadm modify discovery -t disable iscsiadm: logical unit in use iscsiadm: Unable to complete operation (messages) Jun 17 19:02:58 hostname genunix: [ID 408114 kern.info] /iscsi/[EMAIL PROTECTED],6 (sd8) offline Jun 17 19:02:58 hostname genunix: [ID 408114 kern.info] /iscsi/[EMAIL PROTECTED],5 (sd7) offline Jun 17 19:02:58 hostname genunix: [ID 408114 kern.info] /iscsi/[EMAIL PROTECTED],4 (sd6) offline Jun 17 19:02:58 hostname genunix: [ID 408114 kern.info] /iscsi/[EMAIL PROTECTED],3 (sd5) offline Jun 17 19:02:58 hostname genunix: [ID 408114 kern.info] /iscsi/[EMAIL PROTECTED],2 (sd4) offline Jun 17 19:02:58 hostname genunix: [ID 408114 kern.info] /iscsi/[EMAIL PROTECTED],1 (sd2) offline Jun 17 19:02:58 hostname iscsi: [ID 213721 kern.notice] NOTICE: iscsi session(447) - session logout failed (20) # iscsiadm modify discovery -t enable Jun 17 19:03:11 hostname iscsi: [ID 286457 kern.notice] NOTICE: iscsi connection(496) unable to connect to target iqn.1992-08.com.netapp:sn.135019344 (errno:128) Jun 17 19:03:11 hostname genunix: [ID 198094 kern.warning] WARNING: Page83 data not standards compliant NETAPP LUN 0.2 Jun 17 19:03:11 hostname scsi: [ID 799468 kern.info] sd2 at iscsi0: name 0000iqn.1992-08.com.netapp%3Asn.13501934407D0,1, bus address 0000iqn.1992-08.com.netapp%3Asn.13501934407D0,1 Jun 17 19:03:11 hostname genunix: [ID 936769 kern.info] sd2 is /iscsi/[EMAIL PROTECTED],1 Jun 17 19:03:11 hostname genunix: [ID 198094 kern.warning] WARNING: Page83 data not standards compliant NETAPP LUN 0.2 Jun 17 19:03:11 hostname genunix: [ID 408114 kern.info] /iscsi/[EMAIL PROTECTED],1 (sd2) online Jun 17 19:03:11 hostname genunix: [ID 198094 kern.warning] WARNING: Page83 data not standards compliant NETAPP LUN 0.2 Jun 17 19:03:11 hostname scsi: [ID 799468 kern.info] sd4 at iscsi0: name 0000iqn.1992-08.com.netapp%3Asn.13501934407D0,2, bus address 0000iqn.1992-08.com.netapp%3Asn.13501934407D0,2 Jun 17 19:03:11 hostname genunix: [ID 936769 kern.info] sd4 is /iscsi/[EMAIL PROTECTED],2 Jun 17 19:03:11 hostname genunix: [ID 198094 kern.warning] WARNING: Page83 data not standards compliant NETAPP LUN 0.2 Jun 17 19:03:11 hostname genunix: [ID 408114 kern.info] /iscsi/[EMAIL PROTECTED],2 (sd4) online Jun 17 19:03:11 hostname iscsi: [ID 286457 kern.notice] NOTICE: iscsi connection(496) unable to connect to target iqn.1992-08.com.netapp:sn.135019344 (errno:128) # iscsiadm list target -S iqn.1992-08.com.netapp:sn.135019344 Target: iqn.1992-08.com.netapp:sn.135019344 Alias: - TPGT: 1001 ISID: 4000002a0000 Connections: 0 Target: iqn.1992-08.com.netapp:sn.135019344 Alias: moonglow TPGT: 2000 ISID: 4000002a0000 Connections: 1 LUN: 2 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t4d0s2 LUN: 1 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t2d0s2 LUN: 0 Vendor: NETAPP Product: LUN OS Device Name: /dev/rdsk/c2t19d0s2 That was the good news. BUT: Apparently, disabling and enabling the discovery method does have a side effect, which is to somehow reconfigure not only the iscsi initiator, but also other scsi devices. I need to investigate this further, but on another system (which I don't have access to at the moment) a correllation between the method stated above and an "I/O freeze" for approx. a half a minute or more was obvious. Other (traditional) SCSI devices reported Unit Attention in messages and reads had to be reissued. So, as far as my understanding goes so far, disabling / enabling discovery has some negative side effects, which need to be avoided. Does anyone have some good advice on this? Thank you very much in advance. Nils This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
