From owner-freebsd-current@FreeBSD.ORG  Fri Jul 23 19:55:32 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DF63116A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 23 Jul 2004 19:55:32 +0000 (GMT)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8C4CD43D4C
	for <freebsd-current@freebsd.org>;
	Fri, 23 Jul 2004 19:55:32 +0000 (GMT)
	(envelope-from scottl@freebsd.org)
Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12])
	(authenticated bits=0)
	by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6NK1s7h072288;
	Fri, 23 Jul 2004 14:01:54 -0600 (MDT)
	(envelope-from scottl@freebsd.org)
Message-ID: <41016CEE.6060806@freebsd.org>
Date: Fri, 23 Jul 2004 13:54:22 -0600
From: Scott Long <scottl@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7) Gecko/20040514
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Julian Elischer <julian@elischer.org>
References: <200407231632.i6NGWoeO084976@gate.multicom.lv>
	<41016BFC.5000708@elischer.org>
In-Reply-To: <41016BFC.5000708@elischer.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org
cc: freebsd-current@freebsd.org
Subject: Re: Can't check large FS
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jul 2004 19:55:33 -0000

I don't know if I agree with that.  I've fsck'd 1.9TB filesystems with 
no problem.
770MB is quite a bit to be allocating.

Doug might be right about checking an alternate superblock.

Scott

Julian Elischer wrote:

> the process needs to be able to allocate more RAM.
> probably you need to increase its data limit.
> 
> 
> Andris wrote:
> 
>> Hi,
>>
>> I have a PC running 5.2.1-p9 with Promise SX6000 RAID and six 300Gb 
>> Maxtor
>> HDD's configured as RAID 0+1 so the total FS size is about 850 Gb.
>>
>> After hardware failure and rebuilding array I can't check my FS, fsck 
>> always
>> dump core with the message:
>>
>> cannot alloc 775104816 bytes for inoinfo
>> fsck: /dev/pst0s1d: Segmentation fault
>>
>>
>> Andris
>>
>>
>> _______________________________________________
>> freebsd-current@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to 
>> "freebsd-current-unsubscribe@freebsd.org"
>>  
>>
> 
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"