From owner-freebsd-scsi  Fri May 28  4:36:19 1999
Delivered-To: freebsd-scsi@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP id 80ACF14BEF
	for <scsi@FreeBSD.ORG>; Fri, 28 May 1999 04:36:15 -0700 (PDT)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA29921;
	Fri, 28 May 1999 21:35:51 +1000
Date: Fri, 28 May 1999 21:35:51 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199905281135.VAA29921@godzilla.zeta.org.au>
To: bde@zeta.org.au, Don.Lewis@tsc.tdk.com, gibbs@plutotech.com
Subject: Re: FW: -STABLE scsi problem (bug?)
Cc: mauri@aripaev.ee, scsi@FreeBSD.ORG
Sender: owner-freebsd-scsi@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>} >Can't we just walk the buffer list, note the FSes the buffers reference,
>} >and unmount any FSes that aren't referenced?
>} 
>} We could, but syncing can only fail if there is an unexpected problem, so
>} we should be conservative if we don't understand the problem.
>
>I think this is overly conservative.  The unwritten buffers could be
>destined for a dead NFS server, and we could be rebooting to clear the
>stuck mount point.  It could be a definite inconvenience if this forces
>a bunch of huge local filesystems to be fsck'ed.

The nfs case is understood.  Special handling for it was added in
rev.1.42 of kern_shutown.c.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message