On 5 mar, 23:19, Mike Christie <micha...@cs.wisc.edu> wrote: > On 03/03/2010 04:53 AM, Juli n Lliteras wrote: > > > Hi > > > I have some trouble while managing iscsi volumes. I have a host > > virtual server attached to iscsi volume with open-iscsi package. The > > host server have a guest virtual server allocated in the volume > > formatted with ext3 (and is the only initiator connected to). The host > > is a debian lenny. At this stage all is running ok. > > > Next, I simulate a power down problem (rebooting the iscsi target > > only). In result, the guest virtual server hangs few seconds after. > > When target become online again, the virtual server never boot again > > and the host server throw volume filesystem problems. In many > > situations the volume had to be reformatted. > > You want to set > node.session.timeo.replacement_timeout > > higher. If your disconnected from the target longer than that timeout > setting then you are going to hit the same problem though.
Thanks for replying Mike As you said I can rise that value, but is it intended to keep session in a short period disconnection. But for a long term, or a target crash (power failue, kernel hang, ...) this time cannon be known. Would force writes avoid (or minimize) this kind of corruption? is open-iscsi capable to force writes in any manner? Thanks for all Julian(Yartax) -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
