cannot alloc 19968 bytes for inoinfo

[Don Lewis]

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.