Re: fsck_ufs: cannot alloc 3166749884 bytes for inoinfo

On Sun, Feb 27, 2005 at 08:24:15AM +0000, Don Lewis wrote:
> On 26 Feb, Kris Kennaway wrote:
> > A recent panic left my FS with some serious corruption, which fsck is
> > unable to repair:
> > 
> > # fsck_ufs -b 376512 -fy /var
> > Alternate super block location: 376512
> > ** /dev/twed0s1e
> > ** Last Mounted on
> > ** Phase 1 - Check Blocks and Sizes
> > fsck_ufs: cannot alloc 3166749884 bytes for inoinfo
> > 
> > (same holds for any superblock I've tried).
> > 
> > How can I recover from this, short of running newfs?
> 
> What does dumpfs say about the contents of the superblock?  For some
> reason fsck thinks it needs to allocate space to hold the information
> about 791687471 in one cylinder group, which seems a bit unlikely.

I have a similar problem with a 110GB UFS on 5.3/i386.
fsck dies for me with:
fsck_ufs: cannot alloc 607016868 bytes for inoinfo

df output is strange too:
/dev/ad6s1a 113552318 -6315512682 6419980816 -6045%    /vcr

The dumpfs output for the file system is attached;
As you can see, dumpfs dumps core in the end.

Any ideas how to restore this file system without using newfs
are welcome.

Cheers,
 Thomas

P.S.: Please CC me, I'm not on this list.