Date: Tue, 6 Jun 2006 08:12:30 -0500 (CDT) From: "Eric Anderson" <anderson@centtech.com> To: "Robin Elfrink" <elfrink@introweb.nl> Cc: freebsd-isp@freebsd.org Subject: Re: Recovery from disk+fs crash Message-ID: <56782.10.20.200.100.1149599550.squirrel@10.20.200.100> In-Reply-To: <44857BA4.90405@introweb.nl> References: <44852CF1.5070300@introweb.nl> <62208.10.20.200.100.1149598242.squirrel@10.20.200.100> <44857BA4.90405@introweb.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Robin Elfrink said: > Eric Anderson wrote: > >>>root@:~# fsck /dev/da0s1f >>>** /dev/da0s1f (NO WRITE) >>>cannot alloc 18446744067446403432 bytes for inphead > > >> Have you tried using fsck_ffs and specifying an alternate superblock? >> (say 160) > > Yes: > > root@:~# fsck_ffs -b 160 /dev/da0s1f > Alternate super block location: 160 > ** /dev/da0s1f (NO WRITE) > cannot alloc 18446744067446403432 bytes for inphead > > Same error. Something is so badly wrong that fsck wants to allocate a > very big amount of memory. > > I more or less have given up on the illusion of getting data back (that > shows 'em, not letting me have a proper backup system), but still it's > annoying not knowing what is going on and how to fix it. > > > Robin > You could go in with fsdb and fix the parts manually, but it wouldn't be simple. You might also try a 'preen' first - not sure if that will do anything different. Also - this fs is not currently mounted at all, right? Eric -- ------------------------------------------------------------- Eric Anderson anderson@centtech.com Centaur Technology You have my continuous partial attention -------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56782.10.20.200.100.1149599550.squirrel>