HP LeftHand SAN Solutions Support Document - Service Notes - VSA 7.0 for VMware ESX

30
Workaround
Open the Windows Disk Management console and assign a new drive letter to
the volume. The volume should then appear in the directory structure.
Linux-iSCSI Initiator Cannot Reboot When SAN/iQ Volume is
Unavailable (3346)
Scenario
The iSCSI Device Manager hangs when network problems prevent it from
communicating with a storage module. Because the default time-out for
Linux-iSCSI initiator is infinite, the initiator cannot reboot when it is unable
to access the iSCSI volume on the storage module.
Workaround
Restore full network connectivity between iSCSI initiators and storage
modules. If this is not possible, you also can disconnect from the network the
storage module that the initiator can't communicate with. Disconnecting
causes the managers to tell the client that it should stop attempts to contact
that storage module.
If Changing Permissions On An iSCSI Volume, Log On To A New Initiator
Session To Complete The Changes (3326)
Scenario
An iSCSI volume is mounted as a read/write volume and is in use.
You change the access permissions to read-only for the authentication group
in the Console.
The permissions have not changed for the clients that are accessing the
volume. They are still able to write to the volume.
Workaround
To complete the process of changing permissions, log off the current initiator
session for that volume and log on to a new session.