We had an interruption to our iSCSI SAN (a switch rebooted) and I rebooted our Openfiler and XenServers, but after the reboot the XenServers can't mount their drives (but Windows iSCSI clients have no issues).
I can log in to the iSCSI target manually (I've included some sample output below), but no additional /dev/sd devices show up, and no link in /dev/disk/by-id/, which is what Xen refers to. If I create a new volume, target and LUN and then connect that, new devices do appear. Is there any command I need to run on Openfiler to clean up a dirty disconnected target/LUN? Could there be some kind of file-system lock? Any suggestions at all? Here's some info: [EMAIL PROTECTED] ~]# iscsiadm -m node -T iqn.2006-01.com.openfiler:Pool0001_0001 -p 10.1.3.254:3260 -l Login session [iface: default, target: iqn.2006-01.com.openfiler:Pool0001_0001, portal: 10.1.3.254,3260] [EMAIL PROTECTED] ~]# iscsiadm -m session tcp: [8] 10.1.3.254:3260,1 iqn.2006-01.com.openfiler:Pool0001_0001 [EMAIL PROTECTED] ~]# iscsiadm -m session -P 2 iSCSI Transport Class version 2.0-865 iscsiadm version 2.0-865 Target: iqn.2006-01.com.openfiler:Pool0001_0001 Current Portal: 10.1.3.254:3260,1 Persistent Portal: 10.1.3.254:3260,1 ********** Interface: ********** Iface Name: default Iface Transport: tcp Iface IPaddress: 10.1.3.34 Iface HWaddress: default Iface Netdev: default SID: 8 iSCSI Connection State: LOGGED IN Internal iscsid Session State: NO CHANGE ************************ Negotiated iSCSI params: ************************ HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 131072 MaxXmitDataSegmentLength: 131072 FirstBurstLength: 262144 MaxBurstLength: 262144 ImmediateData: No InitialR2T: Yes MaxOutstandingR2T: 1 Thanks in advance! Chris Martin _______________________________________________ Openfiler-users mailing list [email protected] https://lists.openfiler.com/mailman/listinfo/openfiler-users
