Date: Thu, 2 Mar 2006 08:40:07 GMT From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/93942: panic: ufs_dirbad: bad dir Message-ID: <200603020840.k228e7D5031766@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/93942; it has been noted by GNATS.
From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>
To: Kris Kennaway <kris@obsecurity.org>
Cc: David Rhodus <drhodus@machdep.com>,
Dennis Koegel <amf@hobbit.neveragain.de>, FreeBSD-current@freebsd.org,
Martin Machacek <m@m3a.net>, Pawel Jakub Dawidek <pjd@freebsd.org>,
FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/93942: panic: ufs_dirbad: bad dir
Date: Thu, 2 Mar 2006 10:37:34 +0200 (EET)
Hello!
On Wed, 1 Mar 2006, Kris Kennaway wrote:
>> I have been working with the bad dir problem for several months and I
>> have not had corruption which fsck would not correct.
>
> Me either, but that's surely small comfort to Yarema :-)
I think it would be great if originator of this PR tried to mount damaged fs
ro, found broken directory (I think ino 2 is always the root directory,
isn't it?), dumped and analyzed it's contents in order to find out how the
corruption looks like. Then we could at least recreate the result of
the corruption on test filesystem (by binary editing the media) and
teach fsck how to cure such corruptions.
Sincerely, Dmitry
--
Atlantis ISP, System Administrator
e-mail: dmitry@atlantis.dp.ua
nic-hdl: LYNX-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603020840.k228e7D5031766>