From owner-freebsd-stable@FreeBSD.ORG Mon Jun 21 21:06:05 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 CADF016A4CE for ; Mon, 21 Jun 2004 21:06:05 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9564043D41 for ; Mon, 21 Jun 2004 21:06:05 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with spam-scanned (Exim 4.34; FreeBSD) id 1BcVzG-000M41-7g for stable@freebsd.org; Mon, 21 Jun 2004 23:06:04 +0200 Received: from [217.8.136.185] (helo=[192.168.1.10]) by anduin.net with esmtp (Exim 4.34; FreeBSD) id 1BcVzG-000M3y-02 for stable@freebsd.org; Mon, 21 Jun 2004 23:05:54 +0200 Message-ID: <40D74D83.5050904@anduin.net> Date: Mon, 21 Jun 2004 23:05:07 +0200 From: Eirik Oeverby User-Agent: Mozilla Thunderbird 0.6 (X11/20040504) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on anduin.net X-Spam-Status: No, hits=0.0 required=7.5 tests=none autolearn=no version=2.63 X-Spam-Level: Subject: 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:06:05 -0000 Hi, 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. Wbr, /Eirik