Date: Wed, 3 Mar 2004 11:25:36 +1100 From: Tim Robbins <tjr@freebsd.org> To: =?unknown-8bit?Q?Pawe=B3_Ma=B3achowski?= <pawmal-posting@freebsd.lublin.pl> Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: Using read-only NULLFS leads to panic. gdb output included, easy to reproduce. Message-ID: <20040303002536.GA59500@cat.robbins.dropbear.id.au> In-Reply-To: <20040302213936.216CB5F103@shellma.zin.lublin.pl> References: <20040302213936.216CB5F103@shellma.zin.lublin.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 02, 2004 at 10:39:36PM +0100, Pawe Maachowski wrote: > > I know NULLFS is documented as broken and incoming PRs are usually put > in suspended state, awaiting a patch. > However, there are people claiming that using NULLFS in read-only mode > is safe. It seems, they are wrong. [...] > Environmnet: > (A) FreeBSD 4.9-RELEASE, null.ko. > (B) FreeBSD 4.9-STABLE, NULLFS, almost GENERIC (+IPFIREWALL, IPFILTER...) > (C) FreeBSD 4.8-RELEASE, GENERIC, nullfs.ko (+ipfw.ko) [...] There are known bugs in nullfs in all 4.x releases to date, and in 5.0. If I have time, I may MFC the fixes some time before 4.10 is released. Can you reproduce these problems on 5.1 or 5.2? Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040303002536.GA59500>