iscsi /dev/sdb already mounted or /NetApp/Lun busy
 

Hello people,

Ik have a little problem, i'm working on a Red Hat Enterprise Linux Server release 6.5 (Santiago)system (for a storage exam) and i need to connect to a iscsi lun on a NetApp filer (Ontap 8.3).

The Lun was on a older system and for the exam i had to move it to the new storage system. No problem there. The IP of the iSCSI target is not changed, and on the new storage i setup the name of the target the same as the old

When moved i did the following

iscsiadm -m session

iscsiadm -m discovery -t sendtargets -p 10.10.10.18

iscsiadm -m node -T iqn.1992-08.com.netapp:sn.123456789 -p 10.10.10.18:3260 -l

after that i rebooted the linux server

when up again i gave the command: mount to see if all drive where there, but the lun which is /dev/sdb what not there

then i did mount -a

but i got the message /dev/sdb already mounted or /NetApp/Lun busy

i looked in the fstab file (which has not changed)
#
# /etc/fstab
# Created by anaconda on Wed Jan 29 16:02:37 2014
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/VolGroup-lv_root / ext4 defaults 1 1
UUID=e0f3ac5d-7309-4810-a088-abbb3147f125 /boot ext4 defaults 1 2
/dev/mapper/VolGroup-lv_swap swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/sdb /NetApp/Lun ext4 defaults 0 0
10.10.10.11:/vol/vol2/qtree1 /NetApp/EPM1/vol2 nfs defaults 0 0
10.10.10.12:/vol/vol2/qtree3 /NetApp/Camera/vol2 nfs defaults 0 0
10.10.10.12:/vol/vol3/qtree4 /NetApp/Camera/vol3 nfs defaults 0 0


The mtab file is like this

/dev/mapper/VolGroup-lv_root / ext4 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs rw,rootcontext="system_ubject_r:tmpfs_t:s0" 0 0
/dev/sda1 /boot ext4 rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
none /sys/kernel/config configfs rw 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
10.10.10.11:/vol/vol2/qtree1 /NetApp/EPM1/vol2 nfs rw,addr=10.10.10.11 0 0
10.10.10.12:/vol/vol2/qtree3 /NetApp/Camera/vol2 nfs rw,addr=10.10.10.12 0 0
10.10.10.12:/vol/vol3/qtree4 /NetApp/Camera/vol3 nfs rw,addr=10.10.10.12 0 0
nfsd /proc/fs/nfsd nfsd rw 0 0


if i close all sessions, reboot the server the same message is there aleardy mounted ......

i'm at a loss on how to get rid of this message and reconnect to the iSCSI lun, any help for this linux newbe would be helpfull.

Exam, really? I don't know of any college or higher ed institute that really teaches SAN or storage IT skills, like NetAPP. I'm curious to know name of the class and college where you are taking this exam?

You have cross post this same question here:

http://www.linuxquestions.org/questi...sy-4175591206/


Can't tell if you ran the following commands:

At the SAN level or at the OS level? However I googled around and there is a Linux man page for this iscsiadmin command...

I work with a storage person and I've never had to do any type of configuration on the OS side (RHEL) when mapping LUNS to SAN.

To me, these look like NFS shares that the NetApp is mapped to?
I guess I'm having a hard time undestanding where the OS comes in when LUN to LUN.

Yes it is a exam 7mtt exam. (no class or workshop available, just the exam)

You are correct there are also some NFS share maped and those are connecting fine.

The OS was on the "old storage" NetApp Release 8.1.4 7-Mode on the "new storage" it is NetApp Release 8.3RC1

I ran the commands you stated

iscsiadm -m session

iscsiadm -m discovery -t sendtargets -p 10.10.10.18

iscsiadm -m node -T iqn.1992-08.com.netapp:sn.123456789 -p 10.10.10.18:3260 -l

after that i rebooted the linux server


And the discovery and the login is going well, but after the reboot the LUN does not show when i use the mount command. And if i use mount -a (to load all in FSTAB)i get the message iscsi /dev/sdb already mounted or /NetApp/Lun busy

Is the iscsi init script set to run onboot? What's the output of dmesg? Maybe it acquired a new block device name?

In te output from dmesg i can see this about iscsi

scsi 4:0:0:0: Direct-Access NETAPP LUN C-Mode 8300 PQ: 0 ANSI: 5
scsi 3:0:0:0: Direct-Access NETAPP LUN C-Mode 8300 PQ: 0 ANSI: 5
sd 3:0:0:0: Attached scsi generic sg2 type 0
sd 4:0:0:0: Attached scsi generic sg3 type 0
sd 3:0:0:0: [sdb] 8388608 512-byte logical blocks: (4.29 GB/4.00 GiB)
sd 3:0:0:0: [sdb] 4096-byte physical blocks
sd 4:0:0:0: [sdc] 8388608 512-byte logical blocks: (4.29 GB/4.00 GiB)
sd 4:0:0:0: [sdc] 4096-byte physical blocks
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: c2 00 00 08
sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sdb: unknown partition table
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: c2 00 00 08
sd 3:0:0:0: [sdb] Attached SCSI disk
sd 4:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sdc: unknown partition table
sd 4:0:0:0: [sdc] Attached SCSI disk
sd 4:0:0:0: alua: supports implicit TPGS
sd 4:0:0:0: alua: port group 3e9 rel port 05
sd 4:0:0:0: alua: transition timeout set to 120 seconds
sd 4:0:0:0: alua: port group 3e9 state A non-preferred supports TolUsNA
sd 4:0:0:0: alua: Attached
sd 3:0:0:0: alua: supports implicit TPGS
sd 3:0:0:0: alua: port group 3e9 rel port 04
sd 3:0:0:0: alua: transition timeout set to 120 seconds
sd 3:0:0:0: alua: port group 3e9 state A non-preferred supports TolUsNA
sd 3:0:0:0: alua: Attached
alua: device handler registered
device-mapper: multipath round-robin: version 1.0.0 loaded
sd 3:0:0:0: alua: port group 3e9 state A non-preferred supports TolUsNA
sd 4:0:0:0: alua: port group 3e9 state A non-preferred supports TolUsNA