From owner-freebsd-fs@FreeBSD.ORG  Tue Jan 10 17:50:06 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A929E1065672
	for <fs@freebsd.org>; Tue, 10 Jan 2012 17:50:06 +0000 (UTC)
	(envelope-from mckusick@mckusick.com)
Received: from chez.mckusick.com (unknown
	[IPv6:2001:5a8:4:7e72:4a5b:39ff:fe12:452])
	by mx1.freebsd.org (Postfix) with ESMTP id 8CC838FC12
	for <fs@freebsd.org>; Tue, 10 Jan 2012 17:50:06 +0000 (UTC)
Received: from chez.mckusick.com (localhost [127.0.0.1])
	by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id q0AHnn1s053527;
	Tue, 10 Jan 2012 09:49:54 -0800 (PST)
	(envelope-from mckusick@chez.mckusick.com)
Message-Id: <201201101749.q0AHnn1s053527@chez.mckusick.com>
To: "Julian H. Stacey" <jhs@berklix.com>
In-reply-to: <201201101315.q0ADFQ5f017969@fire.js.berklix.net> 
Date: Tue, 10 Jan 2012 09:49:49 -0800
From: Kirk McKusick <mckusick@mckusick.com>
X-Spam-Status: No, score=0.0 required=5.0 tests=MISSING_MID, UNPARSEABLE_RELAY
	autolearn=failed version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on chez.mckusick.com
Cc: fs@freebsd.org
Subject: Re: unexpected soft update inconsistency - cannot fix 
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jan 2012 17:50:06 -0000

The problem is that you somehow lost your ".." entry in the
directory associated with inode 825575. That entry was then
replaced by "Makefile,v". Because ".." is missing, fsck cannot
figure out its parent and hence the pathname of the directory.

To fix, do the following:

cd to mountpoint of filesystem
find . -inum 825575 -print
cd to the directory identified by find
mv Makefile,v Makefile,v.sav
cd /
unmount filesystem
run fsck which should now be able to create ".."
mount filesystem
cd to affected directory
mv Makefile,v.sav Makefile,v

	Kirk McKusick