From owner-freebsd-stable@FreeBSD.ORG Mon Mar 15 02:03:51 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 AFE1216A4CE; Mon, 15 Mar 2004 02:03:51 -0800 (PST) Received: from shellma.zin.lublin.pl (shellma.zin.lublin.pl [212.182.126.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7623243D1D; Mon, 15 Mar 2004 02:03:51 -0800 (PST) (envelope-from pawmal-posting@freebsd.lublin.pl) Received: by shellma.zin.lublin.pl (Postfix, from userid 1018) id C9C055F103; Mon, 15 Mar 2004 11:05:24 +0100 (CET) Date: Mon, 15 Mar 2004 11:05:24 +0100 From: Pawel Malachowski To: Pawel Malachowski Message-ID: <20040315100524.GA80784@shellma.zin.lublin.pl> References: <20040303134001.GA63144@cat.robbins.dropbear.id.au> <200403080858.JAA18049@galaxy.hbg.de.ao-srv.com> <20040309033529.GA88800@cat.robbins.dropbear.id.au> <20040310181933.GA28452@shellma.zin.lublin.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20040310181933.GA28452@shellma.zin.lublin.pl> User-Agent: Mutt/1.4.2i cc: stable@freebsd.org Subject: Re: Using read-only NULLFS leads to panic. gdb output included, e asy to reproduce. 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, 15 Mar 2004 10:03:51 -0000 On Wed, Mar 10, 2004 at 07:19:33PM +0100, Pawel Malachowski wrote: > > Here's the patch against RELENG_4: > > http://people.freebsd.org/~tjr/nullfs-4.diff > > > > It works, but I'm not going to commit it until I've had time to > > check a few things first. > > Successfully tested on my 4.9-STABLE box, thanks. Well, I shoot myself in the foot. After 2 days, my 4.9-RELEASE machine caught o problem again. Not panic, new processess trying to access one of filesystems were stopping at `inode' state (for example >3k crons). System was also not able to shutdown properly. -- Paweł Małachowski