Date: Mon, 15 Mar 2004 11:05:24 +0100 From: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl> To: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl> Cc: stable@freebsd.org Subject: Re: Using read-only NULLFS leads to panic. gdb output included, e asy to reproduce. Message-ID: <20040315100524.GA80784@shellma.zin.lublin.pl> In-Reply-To: <20040310181933.GA28452@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040315100524.GA80784>