Date: Tue, 4 Oct 2005 10:25:32 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-current@freebsd.org Subject: Re: [PANIC] ufs_dirbad: bad dir Message-ID: <20051004172532.GA49048@dragon.NUXI.org> In-Reply-To: <20050926180615.GA61075@xor.obsecurity.org> References: <20050926152952.GA1670@dragon.NUXI.org> <20050926160808.GB1649@dragon.NUXI.org> <20050926180615.GA61075@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 26, 2005 at 02:06:15PM -0400, Kris Kennaway wrote: > On Mon, Sep 26, 2005 at 09:08:08AM -0700, David O'Brien wrote: > > On Mon, Sep 26, 2005 at 08:29:52AM -0700, David O'Brien wrote: > > > Anyone own this one? > > > The running kernel was: > > > FreeBSD 7.0-CURRENT #528: Sun Sep 25 21:07:22 PDT 2005 > > ... > > > panic messages: > > > panic: ufs_dirbad: bad dir > > > > Just got another one - uptime was about 10 minutes. Is one of the recent > > changes to SU & FFS making this situation easier to trigger? > > As I've mentioned the last few times you reported this, it's a > long-standing bug that has existed since the FreeBSD 4.x days or > before. I know you mentioned this. :-) However the rate of my tripping over it has increased to every few days. > Try to fsck -f your filesystems to make sure there is no > lingering damage. I've turned off SU on all my partitions. I also do periodically boot single user and 'fsck -y /<fs>'. We still definitely have at least one serious UFS bug in the weeds. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051004172532.GA49048>