Date: Mon, 26 May 2003 23:51:49 -0700 From: Kris Kennaway <kris@obsecurity.org> To: hackers@FreeBSD.org Subject: Re: Change request for mount_null manpage Message-ID: <20030527065149.GA84791@rot13.obsecurity.org> In-Reply-To: <20030526055024.GN383@hal9000.halplant.com> References: <20030525145542.GA97711@LF.net> <20030526055024.GN383@hal9000.halplant.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030527065149.GA84791>