>>> Iain <[email protected]> schrieb am 04.12.2010 um 21:31 in Nachricht <0e9b8d0d-6d2c-489d-a050-fa3b90605...@h17g2000pre.googlegroups.com>: > 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)
Hi! I'm no expert, but I'd expect the TCP connections (if keep-alive is used) to time out. TCP connections without keep alive will survive when no data exchange happens during suspend. If the non sleeping party times out a connection, the awakening party will see a connection reset on the first packet exchange. I'd expect iSCSI to handle these (ie.e. re-establish a connection). I wonder why new devices are found, 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? A good question is whether any I/O operation on iSCSI devices are tried before the whole network stack is properly restored/reestablished. I don't know the answer, sorry. Regards, Ulrich -- 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.
