From owner-freebsd-current@FreeBSD.ORG  Thu Jun  2 04:53:45 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: 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 1A2B916A41C
	for <freebsd-current@FreeBSD.org>; Thu,  2 Jun 2005 04:53:45 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D6C5A43D53
	for <freebsd-current@FreeBSD.org>; Thu,  2 Jun 2005 04:53:44 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id j524rUtI002411;
	Wed, 1 Jun 2005 21:53:34 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200506020453.j524rUtI002411@gw.catspoiler.org>
Date: Wed, 1 Jun 2005 21:53:30 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: anderson@centtech.com
In-Reply-To: <429E1EAD.8010604@centtech.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Cc: freebsd-current@FreeBSD.org
Subject: Re: cannot alloc 19968 bytes for inoinfo
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Thu, 02 Jun 2005 04:53:45 -0000

On  1 Jun, Eric Anderson wrote:
> Andre Guibert de Bruet wrote:
>> 
>> On Wed, 1 Jun 2005, Eric Anderson wrote:
>> 
>>> Don Lewis wrote:
>>>
>>>> On 31 May, Eric Anderson wrote:
>>>>
>>>>> One of my filesystems won't fsck.  I'm not sure how to fix it, or 
>>>>> what it's really trying to tell me.
>>>>>
>>>>> # fsck -y /vol1
>>>>> ** /dev/da0s1d
>>>>> ** Last Mounted on /vol1
>>>>> ** Phase 1 - Check Blocks and Sizes
>>>>> fsck_ufs: cannot alloc 19968 bytes for inoinfo
>>>>>
>>>>> df -i /vol1 output:
>>>>> Filesystem  1K-blocks        Used    Avail Capacity  iused     ifree 
>>>>> %iused  Mounted on
>>>>> /dev/da0s1d 1891668564 1684163832 56171248    97% 55109756 189360002 
>>>>> 23% /vol1
>>>>>
>>>>> Any help would be very appreciated!
>>>>
>>>>
>>>> You're probably running into the default 512MB data size limit.  Try
>>>> setting kern.maxdsiz to a larger value in /boot/loader.conf and
>>>> rebooting.  I've got mine set to 1GB.
>>>>     kern.maxdsiz="1073741824"
>>>
>>>
>>> Hmm - I don't seem to have that sysctl..  What would create it?
>> 
>> 
>> It's a loader tunable, not a sysctl variable. man 5 loader.conf
> 
> Oh.. oops. :)   Ok, then I have it set correctly but it isn't helping 
> me.  My fsck still dies the same way.  Looks like it's taking up about 
> 362MB memory (I have 1GB).  Any more ideas?

What does the shell limit command say about your datasize limit?  Your
limit might have been cranked down in login.conf.