Date: Tue, 09 Jan 2007 12:14:15 -0500 From: DAve <dave.list@pixelhammer.com> To: Free BSD Questions list <freebsd-questions@freebsd.org> Subject: Re: iSCSI Message-ID: <45A3CD67.6000108@pixelhammer.com> In-Reply-To: <20070109163557.GH41724@dan.emsphone.com> References: <45A2A0E6.7090202@pixelhammer.com> <200701081508.20632.lists@jnielsen.net> <45A399BD.9080707@pixelhammer.com> <20070109163557.GH41724@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Nelson wrote: > 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. > That was my thought as well. I have my pop toasters all mounting a NFS mail store and when NFS goes away I don't have my NFS clients doing a fsck when the mount returns. Not sure if that is important as iSCSI is all new to me, still reading up on it. Does FreeBSD do anything special to a NFS mount when it returns? Should I subscribe to the SCSI list to continue this thread? DAve -- Three years now I've asked Google why they don't have a logo change for Memorial Day. Why do they choose to do logos for other non-international holidays, but nothing for Veterans? Maybe they forgot who made that choice possible.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45A3CD67.6000108>