Re: fsck_ufs: cannot alloc 3166749884 bytes for inoinfo

From: Kris Kennaway <kris_at_obsecurity.org>
Date: Sun, 27 Feb 2005 14:39:35 -0800
On Sun, Feb 27, 2005 at 02:24:06AM -0800, 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 needed to get the machine back up and running so I mounted /var r/o,
copied across data without incident and newfs'ed the filesystem.

Kris


Received on Sun Feb 27 2005 - 21:39:37 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:29 UTC