Disabling iSCSI Targets Can Cause The Host Initiator an Abnormally Long Time To List iSCSI Devices
(Doc ID 1642603.1)
Last updated on MAY 17, 2018
Applies to:Solaris Operating System - Version 10 10/09 U8 and later
Information in this document applies to any platform.
Running an explorer on a host with iSCSI LUNs takes a long time or will hang
or even running ls -l /dev/rdsk/* takes a very long time or hang.
There are a couple of ways the problem can be seen:
A) Disable an existing iSCSI target used as part of a zpool on the host and rebooting the host.
To add a view, the following command is used in COMSTAR
Similarly to disallow host access, the following command can be used.
On boot, run
The system will hang.
Ctrl-C not work.
kill will not work
Reset the initiator box and the system will experience problems will booting
NOTICE: iscsi connection(6) unable to connect to target SENDTARGETS_DISCOVERY
repeats many time
# stmfadm add-view -h host-group-a -t targets-0 -n 1 6000AE40C5000000000046FC4FEA001C
The host is now able to boot.
B) Another way of achieving the same effect:
1. Creating iscsi targets and getting them discovered on the initiator host.
# iscsitadm create target -b /export/home/hoge_X hogeX
2. Recognizing Solaris targets by SendTargets access.
After that, creating the device files under /dev/rdsk by running "devfsadm -C"
# iscsiadm modify discovery -t enable
# devfsadm -C
3. Disable the discovery
3. Then delete some of the iscsi targets using the command
4. Start a discovery of the iscsi targets.
5. Start I/O on a target
6. Bring down the link during i/o access
On the initiator side,
5. On the initiator side, run
The device links of the previous devices under the /dev/*dsk/* will cause the commands to hang.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document