Date: Sat, 8 Jun 1996 21:36:24 -0600 From: Nate Williams <nate@sri.MT.net> To: David Langford <langfod@dihelix.com> Cc: stable@freebsd.org Subject: Re: PANIC with Stable June 7th (bad dir?) Message-ID: <199606090336.VAA05403@rocky.sri.MT.net> In-Reply-To: <199606090316.RAA02635@caliban.dihelix.com> References: <199606090316.RAA02635@caliban.dihelix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> What does the following panic mean? > (i.e where should I start looking to fix it) > > > Jun 8 15:05:02 news /kernel: /news: bad dir ino 144771 at offset 55374: mangledentry > Jun 8 15:05:02 news /kernel: panic: bad dir > Jun 8 15:05:03 news /kernel: > Jun 8 15:05:03 news /kernel: syncing disks... FreeBSD 2.1-STABLE #0: Fri Jun 700:38:56 HST 1996 You should figure out why your partition is hosed. It's possible (nay, probably) that if the machines is shutdown 'incorrectly' (crashed, turned off, power lost, etc..) that the normal 'fsck' process run in -stable won't clean up everything on the disk. You need to re-fsck the disks until they come out clean. This is a genuine bug that is *probably* fixed in current, but given that I'm not 100% sure the fix is correct I didn't bring it into -stable. Or, if you've got a bad cache it will write out bad data to the disk, thus causing panics at random places. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606090336.VAA05403>