From owner-freebsd-hackers@FreeBSD.ORG  Tue Sep 25 18:50:18 2007
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C87DF16A421
	for <freebsd-hackers@FreeBSD.org>; Tue, 25 Sep 2007 18:50:18 +0000 (UTC)
	(envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (adsl-75-1-14-242.dsl.scrm01.sbcglobal.net
	[75.1.14.242]) by mx1.freebsd.org (Postfix) with ESMTP id 7F8D813C46A
	for <freebsd-hackers@FreeBSD.org>; Tue, 25 Sep 2007 18:50:18 +0000 (UTC)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id l8PIo9WJ010198;
	Tue, 25 Sep 2007 11:50:13 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200709251850.l8PIo9WJ010198@gw.catspoiler.org>
Date: Tue, 25 Sep 2007 11:50:09 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: samflanker@gmail.com
In-Reply-To: <46F8B60A.3080901@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Cc: freebsd-hackers@FreeBSD.org
Subject: Re: fsck of large volume with small memory
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Sep 2007 18:50:18 -0000

On 25 Sep, sam wrote:
> Don Lewis wrote:
>> On 24 Sep, sam wrote:
>>   
>>
>>> any solutions ?
>>>     
>>
>> The patch below should allow a manual fsck to run to completion. I'd
>> recommend running "fsck -N" and capturing its output.  Then use the clri
>>   
> # fsck -N
> fsck: illegal option -- N
> usage: fsck [-dfnpvy] [-B | -F] [-T fstype:fsoptions] [-t fstype] 
> [special | node] ...

Sorry, it should be "fsck -n".