From owner-freebsd-fs@FreeBSD.ORG  Wed Mar  2 23:21:52 2005
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 02ED816A4CE
	for <freebsd-fs@freebsd.org>; Wed,  2 Mar 2005 23:21:52 +0000 (GMT)
Received: from tower.berklix.org (bsd.bsn.com [194.221.32.7])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4A5A143D39
	for <freebsd-fs@freebsd.org>; Wed,  2 Mar 2005 23:21:51 +0000 (GMT)
	(envelope-from jhs@berklix.org)
Received: from js.berklix.net (p549A46F9.dip.t-dialin.net [84.154.70.249])
	(authenticated bits=0)
	by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j22NLiYS051059;
	Thu, 3 Mar 2005 00:21:44 +0100 (CET)
	(envelope-from jhs@tower.berklix.net)
Received: from fire.jhs.private (fire.jhs.private [192.168.91.41])
	by js.berklix.net (8.12.11/8.12.11) with ESMTP id j22NMfWX005651;
	Thu, 3 Mar 2005 00:23:06 +0100 (CET)
	(envelope-from jhs@tower.berklix.net)
Received: from fire.jhs.private (localhost [127.0.0.1])
	by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j22NMfdD031805;
	Thu, 3 Mar 2005 00:22:41 +0100 (CET)
	(envelope-from jhs@fire.jhs.private)
Message-Id: <200503022322.j22NMfdD031805@fire.jhs.private>
To: freebsd-fs@freebsd.org
From: "Julian Stacey" <jhs@berklix.org>
Organization: http://berklix.com/~jhs/  Munich Unix, BSD, Internet
User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org
In-reply-to: Your message of "Wed, 02 Mar 2005 00:46:39 +0100."
		<200503012346.j21NkdrU002367@fire.jhs.private> 
Date: Thu, 03 Mar 2005 00:22:41 +0100
Sender: jhs@berklix.org
Subject: Re: A bad lost+found causes fsck of FFS to repeatefly fail. 
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
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: Wed, 02 Mar 2005 23:21:52 -0000

I wrote about 24 hours ago:

> I had a FFS error that fsck couldnt fix, & I've seen similar before:
>   If content of lost+found/ is itself damaged, fsck fails, it seems.
>   Then one has to manually [copy elsewhere] & rm -rf lost+found then re-fsck.
> Should the above be added to man fsck, or
> content below submitted as a send-pr ? Or do readers here
> include FFS / FSCK maintainers ?
> 
> Log & environ follow:
> 
> uname -a
>   FreeBSD fire.jhs.private 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat
>   Feb 26 21:47:28 CET 2005
>   jhs@fire.jhs.private:/usr1/src/sys/amd64/compile/FIRE64.small amd64

Same scenario a day later on another of my hosts !
This one is not a 64bit amd just a normal 686, 
	FreeBSD film.jhs.private 5.3-RELEASE FreeBSD 5.3-RELEASE
	#0: Fri Nov  5 04:19:18 UTC 2004
	root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
& its a 33 Gig instead of 40 Gig partition. Other than that, same story.

-
Julian Stacey        Net & Sys Eng Consultant, Munich       http://berklix.com
Mail in Ascii (Html=Spam).  Ihr Rauch = mein allergischer Kopfschmerz.