From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 11:34:06 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52D3316A418 for ; Tue, 18 Dec 2007 11:34:06 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id C21BF13C4E9 for ; Tue, 18 Dec 2007 11:34:05 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-30-69.lns10.adl2.internode.on.net [121.45.30.69]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id lBIBXsWZ016256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Dec 2007 22:03:55 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Tue, 18 Dec 2007 22:03:42 +1030 User-Agent: KMail/1.9.7 References: <1197889622.4766585626a92@webmail.rawbw.com> <20071218001355.GA40289@marvin.blogreen.org> <20071218055201.GB51227@ace.netcins.ceid.upatras.gr> In-Reply-To: <20071218055201.GB51227@ace.netcins.ceid.upatras.gr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7090266.mINItEd91n"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712182203.49414.doconnor@gsoft.com.au> X-Spam-Score: -2.312 () BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: Nikos Ntarmos Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 11:34:06 -0000 --nextPart7090266.mINItEd91n Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 18 Dec 2007, Nikos Ntarmos wrote: > Off the top of my head, what is wrong/hard with just logging a device > failure, discarding all remaining cached operations, and unmounting > the fs when a disk device goes missing? I understand that this is not > a viable solution for critical filesystems, but I can see nothing > wrong with this approach for removable devices and/or non-critical > fs's. There was a long, long thread which discussed this earlier. It's easy to say what should be done, it's harder to submit patches that=20 clean up the respective failure modes. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart7090266.mINItEd91n Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHZ7Ad5ZPcIHs/zowRArzeAJ4m+0XQGpz9PBei1jYacmjDUyOc/gCfdwS0 DPePtOxwyKrQwIrCU643KEY= =Vg3T -----END PGP SIGNATURE----- --nextPart7090266.mINItEd91n--