From owner-freebsd-current@FreeBSD.ORG Thu Mar 2 08:37:51 2006 Return-Path: X-Original-To: FreeBSD-current@freebsd.org Delivered-To: FreeBSD-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B836216A420; Thu, 2 Mar 2006 08:37:51 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id F04E843D46; Thu, 2 Mar 2006 08:37:50 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k228bYCp008622; Thu, 2 Mar 2006 10:37:34 +0200 (EET) (envelope-from dmitry@atlantis.dp.ua) Date: Thu, 2 Mar 2006 10:37:34 +0200 (EET) From: Dmitry Pryanishnikov To: Kris Kennaway In-Reply-To: <20060301201937.GA29208@xor.obsecurity.org> Message-ID: <20060302102719.A83093@atlantis.atlantis.dp.ua> References: <20060228195343.GA85313@xor.obsecurity.org> <3BD79FAD83E2122EC1644386@ramen.coolrat.org> <20060301201937.GA29208@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: David Rhodus , Pawel Jakub Dawidek , Dennis Koegel , FreeBSD-current@freebsd.org, Martin Machacek , FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/93942: panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2006 08:37:51 -0000 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