Date: Sun, 27 Feb 2005 02:24:06 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: kris@obsecurity.org Cc: current@FreeBSD.org Subject: Re: fsck_ufs: cannot alloc 3166749884 bytes for inoinfo Message-ID: <200502271024.j1RAO6jC010109@gw.catspoiler.org> In-Reply-To: <20050227050523.GA92300@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502271024.j1RAO6jC010109>