Subject: Re: large FFSv2 -> file system corruption
To: None <firstname.lastname@example.org>
From: Jan Schaumann <email@example.com>
Date: 07/25/2004 19:02:02
Content-Type: text/plain; charset=us-ascii
Alistair Crooks <firstname.lastname@example.org> wrote:
> On Wed, Jul 21, 2004 at 10:36:46AM -0400, Jan Schaumann wrote:
> > Eric Haszlakiewicz <email@example.com> wrote:
> > > On Tue, Jul 20, 2004 at 11:04:31PM -0400, Jan Schaumann wrote:
> > > > After newfs'ing the file system using FFSv1, and trying to populate=
> > > > file system, I get a kernel panic:
> > > >=20
> > > > /anon-root: bad dir ino 76362257 at offset 51632: mangled entry
> > > > panic: bad dir =
> > > > Stopped in pid 366.1 (pax) at netbsd:cpu_Debugger+0x1: ret
> > > >=20
> > > > What the hell is going on here?
> > >=20
> > > I recently saw a patch someone posted that adjusted some 32-bit casts
> > > in the ffs code. Perhaps that's what's triggering your problem?
> > Any idea where that patch appeared and which files it patched? Was it
> > commited?
> Take a look at tech-kern for the message id
> "Message-ID: <firstname.lastname@example.org>"
> from Darrin Jewell.
Just for those who are not subscribed to tech-kern: the patch proposed
in this email does in fact seem to fix the problems I've been seeing and
finally makes my machine reliable again.
You can blame it all on the Internet.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----