Date: Thu, 2 Mar 2006 10:37:34 +0200 (EET) From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> To: Kris Kennaway <kris@obsecurity.org> Cc: David Rhodus <drhodus@machdep.com>, Pawel Jakub Dawidek <pjd@freebsd.org>, Dennis Koegel <amf@hobbit.neveragain.de>, FreeBSD-current@freebsd.org, Martin Machacek <m@m3a.net>, FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/93942: panic: ufs_dirbad: bad dir Message-ID: <20060302102719.A83093@atlantis.atlantis.dp.ua> In-Reply-To: <20060301201937.GA29208@xor.obsecurity.org> References: <courier.44046DC8.000006A2@CoolRat.org> <20060228195343.GA85313@xor.obsecurity.org> <3BD79FAD83E2122EC1644386@ramen.coolrat.org> <fe77c96b0603011210w439e1d11xb82e3498c1846e65@mail.gmail.com> <20060301201937.GA29208@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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?20060302102719.A83093>