Hi there,
I got a phantom lun showing up in my messages file when starting the iSCSI service:
-------- [root@blue snapdrive]# sanlun lun show no filer LUNs available -------- snap1> lun show snap1> version NetApp Release 7.2.1: Sun Dec 10 00:23:08 PST 2006 -------- iscsi service start:
Apr 26 09:22:24 blue iscsi: iscsi config check succeeded Apr 26 09:22:24 blue kernel: iscsi-sfnet: Loading iscsi_sfnet version 4:0.1.11-3 Apr 26 09:22:24 blue kernel: iscsi-sfnet: Control device major number 254 Apr 26 09:22:24 blue iscsi: Loading iscsi driver: succeeded Apr 26 09:22:29 blue iscsid[4950]: version 4:0.1.11-3 variant (02-May-2006) Apr 26 09:22:29 blue iscsi: iscsid startup succeeded Apr 26 09:22:29 blue iscsid[4954]: Connected to Discovery Address 192.168.1.81 Apr 26 09:22:29 blue kernel: iscsi-sfnet:host4: Session established Apr 26 09:22:29 blue kernel: scsi4 : SFNet iSCSI driver Apr 26 09:22:29 blue kernel: scsi: unknown device type 31 Apr 26 09:22:29 blue kernel: Vendor: NETAPP Model: LUN Rev: 0.2 Apr 26 09:22:29 blue kernel: Type: Unknown ANSI SCSI revision: 04 Apr 26 09:24:59 blue ntpd[3373]: kernel time sync enabled 0001 ---
Where does it get it from? This happened after a crash of the linux box while I was testing some multipathing. This in hindering other operations like mounting new luns etc.
-Theo
What is the result of "iscsi show initiator" on the filer?
-----Original Message----- From: Theo Dijkstra [mailto:dijxtra@xs4all.nl] Sent: Thursday, April 26, 2007 3:41 AM To: toasters@mathworks.com Subject: Phantom LUN
Hi there,
I got a phantom lun showing up in my messages file when starting the iSCSI service:
-------- [root@blue snapdrive]# sanlun lun show no filer LUNs available -------- snap1> lun show snap1> version NetApp Release 7.2.1: Sun Dec 10 00:23:08 PST 2006 -------- iscsi service start:
Apr 26 09:22:24 blue iscsi: iscsi config check succeeded Apr 26 09:22:24 blue kernel: iscsi-sfnet: Loading iscsi_sfnet version 4:0.1.11-3 Apr 26 09:22:24 blue kernel: iscsi-sfnet: Control device major number 254 Apr 26 09:22:24 blue iscsi: Loading iscsi driver: succeeded Apr 26 09:22:29 blue iscsid[4950]: version 4:0.1.11-3 variant (02-May-2006) Apr 26 09:22:29 blue iscsi: iscsid startup succeeded Apr 26 09:22:29 blue iscsid[4954]: Connected to Discovery Address 192.168.1.81 Apr 26 09:22:29 blue kernel: iscsi-sfnet:host4: Session established Apr 26 09:22:29 blue kernel: scsi4 : SFNet iSCSI driver Apr 26 09:22:29 blue kernel: scsi: unknown device type 31 Apr 26 09:22:29 blue kernel: Vendor: NETAPP Model: LUN
Rev: 0.2 Apr 26 09:22:29 blue kernel: Type: Unknown
ANSI SCSI revision: 04 Apr 26 09:24:59 blue ntpd[3373]: kernel time sync enabled 0001 ---
Where does it get it from? This happened after a crash of the linux box while I was testing some multipathing. This in hindering other operations like mounting new luns etc.
-Theo
---------- snap1> iscsi show initiator iscsi show initiator: This command has been deprecated. Please consider using 'iscsi initiator show' instead.
Initiators connected: TSIH TPGroup Initiator 46 2000 blue (iqn.1987-05.com.cisco:blue / 00:02:3d:00:00:01) ---------- snap1> snap1> lun show ------------
But I think this is more a linux side problem. It has a definition for a device (lun) somewhere and I can't get rid of it:
---------- snap1> Connection closed by foreign host. [root@blue etc]# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: SAMSUNG SP2504C Rev: VT10 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: SAMSUNG SP2504C Rev: VT10 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi4 Channel: 00 Id: 00 Lun: 00 Vendor: NETAPP Model: LUN Rev: 0.2 Type: Unknown ANSI SCSI revision: 04 ------------
On Thu, April 26, 2007 14:24, Rozumny, Vic wrote:
What is the result of "iscsi show initiator" on the filer?
-----Original Message----- From: Theo Dijkstra [mailto:dijxtra@xs4all.nl] Sent: Thursday, April 26, 2007 3:41 AM To: toasters@mathworks.com Subject: Phantom LUN
Hi there,
I got a phantom lun showing up in my messages file when starting the iSCSI service:
[root@blue snapdrive]# sanlun lun show no filer LUNs available
snap1> lun show snap1> version NetApp Release 7.2.1: Sun Dec 10 00:23:08 PST 2006
iscsi service start:
Apr 26 09:22:24 blue iscsi: iscsi config check succeeded Apr 26 09:22:24 blue kernel: iscsi-sfnet: Loading iscsi_sfnet version 4:0.1.11-3 Apr 26 09:22:24 blue kernel: iscsi-sfnet: Control device major number 254 Apr 26 09:22:24 blue iscsi: Loading iscsi driver: succeeded Apr 26 09:22:29 blue iscsid[4950]: version 4:0.1.11-3 variant (02-May-2006) Apr 26 09:22:29 blue iscsi: iscsid startup succeeded Apr 26 09:22:29 blue iscsid[4954]: Connected to Discovery Address 192.168.1.81 Apr 26 09:22:29 blue kernel: iscsi-sfnet:host4: Session established Apr 26 09:22:29 blue kernel: scsi4 : SFNet iSCSI driver Apr 26 09:22:29 blue kernel: scsi: unknown device type 31 Apr 26 09:22:29 blue kernel: Vendor: NETAPP Model: LUN
Rev: 0.2 Apr 26 09:22:29 blue kernel: Type: Unknown
ANSI SCSI revision: 04 Apr 26 09:24:59 blue ntpd[3373]: kernel time sync enabled 0001
Where does it get it from? This happened after a crash of the linux box while I was testing some multipathing. This in hindering other operations like mounting new luns etc.
-Theo
Hmmm...not sure how we could hunt this down. The initiator should tell you which server the host is running on, from there you could list all of the current mappings to the server, which should narrow it down some, but unless you have a script that can go out on the wire and query all of the linux clients then.....
If you had time you could offline the LUN and see who complains?
-----Original Message----- From: Theo Dijkstra [mailto:dijxtra@xs4all.nl] Sent: Thursday, April 26, 2007 8:32 AM To: Rozumny, Vic Cc: theo.dijkstra@xs4all.nl; toasters@mathworks.com Subject: RE: Phantom LUN
---------- snap1> iscsi show initiator iscsi show initiator: This command has been deprecated. Please consider using 'iscsi initiator show' instead.
Initiators connected: TSIH TPGroup Initiator 46 2000 blue (iqn.1987-05.com.cisco:blue / 00:02:3d:00:00:01) ---------- snap1> snap1> lun show ------------
But I think this is more a linux side problem. It has a definition for a device (lun) somewhere and I can't get rid of it:
---------- snap1> Connection closed by foreign host. [root@blue etc]# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: SAMSUNG SP2504C Rev: VT10 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: SAMSUNG SP2504C Rev: VT10 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi4 Channel: 00 Id: 00 Lun: 00 Vendor: NETAPP Model: LUN Rev: 0.2 Type: Unknown ANSI SCSI revision: 04 ------------
On Thu, April 26, 2007 14:24, Rozumny, Vic wrote:
What is the result of "iscsi show initiator" on the filer?
-----Original Message----- From: Theo Dijkstra [mailto:dijxtra@xs4all.nl] Sent: Thursday, April 26, 2007 3:41 AM To: toasters@mathworks.com Subject: Phantom LUN
Hi there,
I got a phantom lun showing up in my messages file when starting the iSCSI service:
[root@blue snapdrive]# sanlun lun show no filer LUNs available
snap1> lun show snap1> version NetApp Release 7.2.1: Sun Dec 10 00:23:08 PST 2006
iscsi service start:
Apr 26 09:22:24 blue iscsi: iscsi config check succeeded Apr 26 09:22:24 blue kernel: iscsi-sfnet: Loading iscsi_sfnet version 4:0.1.11-3 Apr 26 09:22:24 blue kernel: iscsi-sfnet: Control device major number 254 Apr 26 09:22:24 blue iscsi: Loading iscsi driver: succeeded Apr 26 09:22:29 blue iscsid[4950]: version 4:0.1.11-3 variant (02-May-2006) Apr 26 09:22:29 blue iscsi: iscsid startup succeeded Apr 26 09:22:29 blue iscsid[4954]: Connected to Discovery Address 192.168.1.81 Apr 26 09:22:29 blue kernel: iscsi-sfnet:host4: Session established Apr 26 09:22:29 blue kernel: scsi4 : SFNet iSCSI driver Apr 26 09:22:29 blue kernel: scsi: unknown device type 31 Apr 26 09:22:29 blue kernel: Vendor: NETAPP Model: LUN
Rev: 0.2 Apr 26 09:22:29 blue kernel: Type: Unknown
ANSI SCSI revision: 04 Apr 26 09:24:59 blue ntpd[3373]: kernel time sync enabled 0001
Where does it get it from? This happened after a crash of the linux box while I was testing some multipathing. This in hindering other operations like mounting new luns etc.
-Theo
-
Rozumny, Vic -
Theo Dijkstra