Date: Sun, 27 Feb 2005 14:39:35 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Don Lewis <truckman@FreeBSD.org> Cc: kris@obsecurity.org Subject: Re: fsck_ufs: cannot alloc 3166749884 bytes for inoinfo Message-ID: <20050227223935.GA48482@xor.obsecurity.org> In-Reply-To: <200502271024.j1RAO6jC010109@gw.catspoiler.org> References: <20050227050523.GA92300@xor.obsecurity.org> <200502271024.j1RAO6jC010109@gw.catspoiler.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCIkwnWry0BWjoQKURAoFuAKDE/b27EsPSjd+QqZ5y/B57W1gtSACgraeZ GK4F6rlBvyitriJ1+It1ljI= =UXox -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050227223935.GA48482>