On 12/04/2010 02:31 PM, Iain wrote:
Hi All,

I'm currently experimenting with exporting an iscsi lun to a desktop
(running ubuntu). This generally works well, however, part of the
daily use of this desktop is that it is suspended to ram then resumed
some time later.

When going through a suspend / resume cycle I notice afterwards that
the iscsi devices are either:

* Not available without restarting the iscsi service
* Available but now have a different device name (eg. a move from sdb
to sdc)

The iscsi layer does not remove devices, so it might be a distro script that is logging in and out of the target or restarting the service and causing devices to get renamed.

The renaming should be a problem, because you should use udev names with iscsi. However, if the devices are actually removed and recreated (this happens with a logout+login) then if there are filessystems or apps using the iscsi device then you will hit problems because the underlying kernel structs are changed. Using dm-multipath over iscsi should workaround those problems though.



I've been looking for documentation / bugs relating to this but I've
not found anything very helpful (Maybe I'm not looking in the right
places).

Thinking about it, I'm wondering if this particular use case is
expected to work or not. Would anyone be able to shed any light on
this?

I do not test that case. I think it works though, because I have got bug reports on RHEL about it before. However, I just tried it on fedora 14 and the suspend did not work for me. It seems if iscsi is running, suspend hangs waiting for something (did not dig into it).

For your setup, when resume is done is iscsid running and what is the connection, session and iscsid state that gets printed out when you run "iscsiadm -m session -P 3".

What do you mean iscsi devices are not available? Is the /dev/sdX node gone? If you access the device does it return IO errors?

--
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to