From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 23:51:51 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D54937B401 for ; Mon, 26 May 2003 23:51:51 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-104-32.dsl.lsan03.pacbell.net [64.169.104.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A08143FD7 for ; Mon, 26 May 2003 23:51:50 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 02AE866B9B for ; Mon, 26 May 2003 23:51:50 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id DFBB6AEA; Mon, 26 May 2003 23:51:49 -0700 (PDT) Date: Mon, 26 May 2003 23:51:49 -0700 From: Kris Kennaway To: hackers@FreeBSD.org Message-ID: <20030527065149.GA84791@rot13.obsecurity.org> References: <20030525145542.GA97711@LF.net> <20030526055024.GN383@hal9000.halplant.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20030526055024.GN383@hal9000.halplant.com> User-Agent: Mutt/1.4.1i Subject: Re: Change request for mount_null manpage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 06:51:51 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 26, 2003 at 01:50:24AM -0400, Andrew J Caines wrote: > Marc, >=20 > > I'm using mount_null now for some months - and i never had a problem wi= th this. >=20 > Are you using it for rw mounts and if so, then what kind or write volume > and sizes do you handle? >=20 > Usually when this comes up, folks are using null ro mounts and the rare > (and sometime unintentional) rw mounts do little or no writing. If anyone > is doing significant volume or size writes, then I've not heared mention > of it. nullfs may well work for some r/o workloads, but it is definitely broken for rw mounts. If anyone is seriously interested in fixing it, I can describe the usage pattern that causes a reliable deadlock on my machine (I've reported it before). Kris --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+0wsFWry0BWjoQKURAqJGAJ48BIm7FIXqfFikgVwIsWskAzq4VgCgyIt9 NksDSSsm9++snMF0ma/13n0= =QFIr -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o--