Date: Tue, 9 Jan 2007 10:35:57 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: DAve <dave.list@pixelhammer.com> Cc: Free BSD Questions list <freebsd-questions@freebsd.org> Subject: Re: iSCSI Message-ID: <20070109163557.GH41724@dan.emsphone.com> In-Reply-To: <45A399BD.9080707@pixelhammer.com> References: <45A2A0E6.7090202@pixelhammer.com> <200701081508.20632.lists@jnielsen.net> <45A399BD.9080707@pixelhammer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jan 09), DAve said: > The developers response, for those who are interested. > > hi Dave, > the initiator for iSCSI will hit stable/current real soon now. > that was the good news, now for the down side: > what was missing all along was recovery from network disconnects, so > while I think I have it almost worked out, I've come across a major > flow in the iscsi design: > when the targets crashes, and comes back, there is no way > to tell the client to run an fsck. This is not a problem if the > client is mounting the iscsi partition read only. > > danny Why should the client need to do an fsck? From its point of view it should just look like the target had the iSCSI equivalent of a bus reset. It should resend any queued requests and continue. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070109163557.GH41724>