From owner-freebsd-bugs@FreeBSD.ORG Thu Mar 2 08:40:08 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A89B816A420 for ; Thu, 2 Mar 2006 08:40:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7731D43D46 for ; Thu, 2 Mar 2006 08:40:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k228e7rv031767 for ; Thu, 2 Mar 2006 08:40:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k228e7D5031766; Thu, 2 Mar 2006 08:40:07 GMT (envelope-from gnats) Date: Thu, 2 Mar 2006 08:40:07 GMT Message-Id: <200603020840.k228e7D5031766@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Dmitry Pryanishnikov Cc: Subject: Re: kern/93942: panic: ufs_dirbad: bad dir X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dmitry Pryanishnikov List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2006 08:40:08 -0000 The following reply was made to PR kern/93942; it has been noted by GNATS. From: Dmitry Pryanishnikov To: Kris Kennaway Cc: David Rhodus , Dennis Koegel , FreeBSD-current@freebsd.org, Martin Machacek , Pawel Jakub Dawidek , 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