From owner-freebsd-bugs@FreeBSD.ORG  Wed Mar 22 03:20:19 2006
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
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 D83BA16A422
	for <freebsd-bugs@hub.freebsd.org>;
	Wed, 22 Mar 2006 03:20:19 +0000 (UTC)
	(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 A414C43D45
	for <freebsd-bugs@hub.freebsd.org>;
	Wed, 22 Mar 2006 03:20:19 +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 k2M3KITJ057312
	for <freebsd-bugs@freefall.freebsd.org>; Wed, 22 Mar 2006 03:20:18 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2M3KITI057311;
	Wed, 22 Mar 2006 03:20:18 GMT (envelope-from gnats)
Date: Wed, 22 Mar 2006 03:20:18 GMT
Message-Id: <200603220320.k2M3KITI057311@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Bruce Evans <bde@zeta.org.au>
Cc: 
Subject: Re: bin/94810: fsck incorrectly reports 'file system marked clean'
 when lost+found fills up
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bruce Evans <bde@zeta.org.au>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2006 03:20:19 -0000

The following reply was made to PR bin/94810; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: Kris Kennaway <kris@freebsd.org>
Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-bugs@freebsd.org
Subject: Re: bin/94810: fsck incorrectly reports 'file system marked clean'
 when lost+found fills up
Date: Wed, 22 Mar 2006 14:10:03 +1100 (EST)

 On Tue, 21 Mar 2006, Kris Kennaway wrote:
 
 >> Description:
 >
 > In cases of severe filesystem damage, fsck may fill up lost+found:
 >
 > [...]
 > SORRY. NO SPACE IN lost+found DIRECTORY
 > UNEXPECTED SOFT UPDATE INCONSISTENCY
 >
 >
 > UNREF DIR  I=871505  OWNER=root MODE=40770
 > SIZE=512 MTIME=Jan  1 09:59 1970
 > RECONNECT? yes
 >
 > SORRY. NO SPACE IN lost+found DIRECTORY
 > UNEXPECTED SOFT UPDATE INCONSISTENCY
 > [...]
 >
 > However, when fsck eventually completes it reports
 >
 > ***** FILE SYSTEM MARKED CLEAN *****
 > ***** FILE SYSTEM WAS MODIFIED *****
 >
 > In fact, all of the damage was not repaired since the extra files
 > could not be reconnected to lost+found, so it is necessary to:
 >
 > 1) mount and clean out lost+found or move it aside
 >
 > 2) unmount and rerun fsck to continue recovering lost files.
 >
 > 3) Repeat until all files have been recovered (may take multiple
 > iterations)
 
 Steps 2 and 3 seemed to be unnecessary when I ran fsck with -y.  Then
 seemed to just delete everything that couldn't be reconnected to
 lost+found, and fsck's claim to have cleaned the file system seemed
 to be correct because the deletions worked.
 
 Another problem with fsck -y is that you have to use it too much because
 the interactive interface for answering y/n doesn't scale to large file
 systems with relatively small but absolutely large damage.  fsck -y should
 only be used for disposable file systems, but even then you might want to
 try to preserve 2 files without interactively answering y/n up to N*2^32
 times for the ones you don't care about.
 
 Bruce