Date: Tue, 06 Jun 2006 14:57:08 +0200 From: Robin Elfrink <elfrink@introweb.nl> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-isp@freebsd.org Subject: Re: Recovery from disk+fs crash Message-ID: <44857BA4.90405@introweb.nl> In-Reply-To: <62208.10.20.200.100.1149598242.squirrel@10.20.200.100> References: <44852CF1.5070300@introweb.nl> <62208.10.20.200.100.1149598242.squirrel@10.20.200.100>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44857BA4.90405>