From owner-freebsd-bugs@FreeBSD.ORG  Thu Apr 26 16:27:57 2007
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
X-Original-To: freebsd-bugs@FreeBSD.org
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 110C416A401
	for <freebsd-bugs@FreeBSD.org>; Thu, 26 Apr 2007 16:27:57 +0000 (UTC)
	(envelope-from dan@more.net)
Received: from jane.spg.more.net (jane.spg.more.net [207.160.133.140])
	by mx1.freebsd.org (Postfix) with ESMTP id D74A013C455
	for <freebsd-bugs@FreeBSD.org>; Thu, 26 Apr 2007 16:27:56 +0000 (UTC)
	(envelope-from dan@more.net)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by jane.spg.more.net (Postfix) with ESMTP id 144239C127;
	Thu, 26 Apr 2007 11:27:54 -0500 (CDT)
From: Dan D Niles <dan@more.net>
To: Mark Linimon <linimon@FreeBSD.org>
In-Reply-To: <200704252230.l3PMUPRr065400@freefall.freebsd.org>
References: <200704252230.l3PMUPRr065400@freefall.freebsd.org>
Content-Type: text/plain
Date: Thu, 26 Apr 2007 11:27:53 -0500
Message-Id: <1177604873.5940.20.camel@jane.spg.more.net>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.1 
Content-Transfer-Encoding: 7bit
Cc: freebsd-bugs@FreeBSD.org
Subject: Re: bin/111146: fsck fails on 6T filesystem
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: Thu, 26 Apr 2007 16:27:57 -0000

On Wed, 2007-04-25 at 22:30 +0000, Mark Linimon wrote:
> Synopsis: fsck fails on 6T filesystem
> 
> State-Changed-From-To: open->feedback
> State-Changed-By: linimon
> State-Changed-When: Wed Apr 25 22:28:39 UTC 2007
> State-Changed-Why: 
> To submitter: did the fsck fix this problem?

The fsck did not fix the problem.  It stopped part way through, with the
errror "fsck_ffs: bad inode number 53321728 to nextinode."  It did not
run out of memory however.

I ran out of time and had to newfs the array.  As a test, I ran fsck on
the clean filesystem populated with the same data.  The most memory it
ever used was 543M.

Dan