From owner-freebsd-questions@FreeBSD.ORG Tue Jan 9 16:36:19 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 43CE016A412 for ; Tue, 9 Jan 2007 16:36:19 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id 0801C13C465 for ; Tue, 9 Jan 2007 16:36:18 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.6/8.13.8) id l09GZvgi097949; Tue, 9 Jan 2007 10:35:57 -0600 (CST) (envelope-from dan) Date: Tue, 9 Jan 2007 10:35:57 -0600 From: Dan Nelson To: DAve Message-ID: <20070109163557.GH41724@dan.emsphone.com> References: <45A2A0E6.7090202@pixelhammer.com> <200701081508.20632.lists@jnielsen.net> <45A399BD.9080707@pixelhammer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45A399BD.9080707@pixelhammer.com> X-OS: FreeBSD 6.2-PRERELEASE User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Free BSD Questions list 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 16:36:19 -0000 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