From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 1 15:47:27 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98C0216A41F for ; Thu, 1 Dec 2005 15:47:27 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A364B43D5A for ; Thu, 1 Dec 2005 15:47:16 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jB1Fl8KB019020; Thu, 1 Dec 2005 08:47:09 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <438F1AFC.1080301@samsco.org> Date: Thu, 01 Dec 2005 08:47:08 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Jacob References: <438C750D.5030604@persistent.co.in> <7579f7fb0511291020qc3c00c6v552fdd6c55d5574b@mail.gmail.com> <438D4AF9.7040600@persistent.co.in> <7579f7fb0511301933j2593b780wf3130bbcb37ab43f@mail.gmail.com> In-Reply-To: <7579f7fb0511301933j2593b780wf3130bbcb37ab43f@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: isp driver - inquiry changed X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 15:47:27 -0000 Matthew Jacob wrote: > Switch as in 'Fabric' or 'Segmented FC-AL'? > > The panic looks like the ones where as far as the system is concerned the > disk went away. > > Right now, certain fabric and loop events cause the isp driver to think the > target has gone away, and this gets sent as async event upstream. I'm > beginning to think that this is a losing proposition for FreeBSD- on the > other hand, the unexpected disappearance of a device isn't handled well by > FreeBSD *either*. Yeah, the most serious and hard to fix problem is that most filesystems and I/O related parts of the VM assume that all I/O succeeds. > > When I did a hardening exercise at Mirapoint for the FreeBSD isp driver and > SCSI midlayer, I seem to recall that I put in a deferred device > disappearance algorithm. Maybe I should check with Mirapoint to see if I can > pull that code back. > John Polstra committed some fixes about a month ago related to device disappearance in SCSI. Might be good to look at that too. Scott