From owner-freebsd-questions@FreeBSD.ORG Tue Jan 9 17:14:21 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BB87216A494 for ; Tue, 9 Jan 2007 17:14:21 +0000 (UTC) (envelope-from dave.list@pixelhammer.com) Received: from ecluster6.tls.net (ecluster6.tls.net [65.196.224.136]) by mx1.freebsd.org (Postfix) with SMTP id 6595513C442 for ; Tue, 9 Jan 2007 17:14:21 +0000 (UTC) (envelope-from dave.list@pixelhammer.com) Received: (qmail 30196 invoked by uid 89); 9 Jan 2007 17:13:20 -0000 Received: from 208-70-43-96.bb.hrtc.net (HELO ?192.168.0.103?) (ldg%tls.net@208.70.43.96) by auth-ecluster6.tls.net with SMTP; 9 Jan 2007 17:13:20 -0000 Message-ID: <45A3CD67.6000108@pixelhammer.com> Date: Tue, 09 Jan 2007 12:14:15 -0500 From: DAve User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Free BSD Questions list References: <45A2A0E6.7090202@pixelhammer.com> <200701081508.20632.lists@jnielsen.net> <45A399BD.9080707@pixelhammer.com> <20070109163557.GH41724@dan.emsphone.com> In-Reply-To: <20070109163557.GH41724@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: iSCSI X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 17:14:21 -0000 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.