From owner-freebsd-bugs@FreeBSD.ORG  Sun Jan  8 15:59:45 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 3D41216A41F;
	Sun,  8 Jan 2006 15:59:45 +0000 (GMT)
	(envelope-from netchild@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9EE2343D48;
	Sun,  8 Jan 2006 15:59:44 +0000 (GMT)
	(envelope-from netchild@FreeBSD.org)
Received: from freefall.freebsd.org (netchild@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k08FxiKS080154;
	Sun, 8 Jan 2006 15:59:44 GMT
	(envelope-from netchild@freefall.freebsd.org)
Received: (from netchild@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k08FxiiS080150;
	Sun, 8 Jan 2006 15:59:44 GMT (envelope-from netchild)
Date: Sun, 8 Jan 2006 15:59:44 GMT
From: Alexander Leidinger <netchild@FreeBSD.org>
Message-Id: <200601081559.k08FxiiS080150@freefall.freebsd.org>
To: lserinol@yahoo.com, netchild@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc: 
Subject: Re: bin/66261: fsck cannot recover filesystem corruption
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
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: Sun, 08 Jan 2006 15:59:45 -0000

Synopsis: fsck cannot recover filesystem corruption

State-Changed-From-To: open->analyzed
State-Changed-By: netchild
State-Changed-When: Sun Jan 8 15:54:28 UTC 2006
State-Changed-Why: 
fsck is known to need a lot of memory for large filesystems. The only
way to solve this is to add memory to the system (you don't have that
much resources at the time a "foreground" fsck is running, for a bgfsck
you can use swap).

It is not known to me if a rewrite of fsck with low memory usage in mind
can solve the issue or not (it may be the case that the memory usage
is inherent in the way fsck works).

http://www.freebsd.org/cgi/query-pr.cgi?pr=66261