From owner-freebsd-stable@FreeBSD.ORG Tue Aug 10 21:06:11 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 1018916A4CE for ; Tue, 10 Aug 2004 21:06:11 +0000 (GMT) Received: from totem.fix.no (totem.fix.no [80.91.36.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF35543D41 for ; Tue, 10 Aug 2004 21:06:10 +0000 (GMT) (envelope-from anders@FreeBSD.org) Received: from localhost (totem.fix.no [80.91.36.20]) by totem.fix.no (Postfix) with ESMTP id B8B0D6A9015; Tue, 10 Aug 2004 23:06:08 +0200 (CEST) Received: from totem.fix.no ([80.91.36.20]) by localhost (totem.fix.no [80.91.36.20]) (amavisd-new, port 10024) with LMTP id 36225-01-2; Tue, 10 Aug 2004 23:06:08 +0200 (CEST) Received: by totem.fix.no (Postfix, from userid 1000) id 801F86A9007; Tue, 10 Aug 2004 23:06:08 +0200 (CEST) Date: Tue, 10 Aug 2004 23:06:08 +0200 From: Anders Nordby To: Eirik Oeverby Message-ID: <20040810210608.GB50556@totem.fix.no> References: <40D74D83.5050904@anduin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40D74D83.5050904@anduin.net> X-PGP-Key: http://anders.fix.no/pgp/ X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD 19C5 D12A BC9F 0083 5956 User-Agent: Mutt/1.5.6i 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: Tue, 10 Aug 2004 21:06:11 -0000 Hi, On Mon, Jun 21, 2004 at 11:05:07PM +0200, Eirik Oeverby wrote: > Since upgrading to 4.10-ish (cvsup), nullfs (mount_null) causes my > jailing host to panic and reboot very frequently. I've been using nullfs > for about a year now, up until and including 4.9 and beyond, and I have > never had problems with it. It has been heavily used, among other things > to mount the host ports tree into all jails (10+), etc. > > Anyone got any idea what's happening? Someone mentioned on -CURRENT that > nullfs has been the victim of some pretty hefty bitrot lately, so > perhaps that's the reason? In any case - in its current form it does not > belong anywhere near a -STABLE release. Did you look at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/63662 and the patch that it mentions, http://people.freebsd.org/~tjr/nullfs-4.diff? Cheers, -- Anders.