From owner-freebsd-stable@FreeBSD.ORG Mon Jun 21 21:09:54 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4721116A4CE for ; Mon, 21 Jun 2004 21:09:54 +0000 (GMT) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B75743D39 for ; Mon, 21 Jun 2004 21:09:54 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-63-207-60-35.dsl.lsan03.pacbell.net [63.207.60.35])i5LL9nlM024379; Mon, 21 Jun 2004 17:09:49 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0DDC951955; Mon, 21 Jun 2004 14:09:48 -0700 (PDT) Date: Mon, 21 Jun 2004 14:09:48 -0700 From: Kris Kennaway To: Eirik Oeverby Message-ID: <20040621210948.GA1043@xor.obsecurity.org> References: <40D74D83.5050904@anduin.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <40D74D83.5050904@anduin.net> User-Agent: Mutt/1.4.2.1i cc: stable@freebsd.org Subject: Re: nullfs in 4.10 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2004 21:09:54 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 21, 2004 at 11:05:07PM +0200, Eirik Oeverby wrote: > Hi, >=20 > Since upgrading to 4.10-ish (cvsup), nullfs (mount_null) causes my=20 > jailing host to panic and reboot very frequently. I've been using nullfs= =20 > for about a year now, up until and including 4.9 and beyond, and I have= =20 > never had problems with it. It has been heavily used, among other things= =20 > to mount the host ports tree into all jails (10+), etc. >=20 > Anyone got any idea what's happening? Someone mentioned on -CURRENT that= =20 > nullfs has been the victim of some pretty hefty bitrot lately, so=20 > perhaps that's the reason? In any case - in its current form it does not= =20 > belong anywhere near a -STABLE release. Which is precisely what the manpage tells you. Kris --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA106cWry0BWjoQKURAmEjAJ4vua3EJd4lrpMamuFeB2mlk+AYkACg5cH8 hp7+LyUYO1b0EFlURmqVyiM= =pgpu -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE--