Date: Tue, 6 Jun 2006 07:50:42 -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: <62208.10.20.200.100.1149598242.squirrel@10.20.200.100> In-Reply-To: <44852CF1.5070300@introweb.nl> References: <44852CF1.5070300@introweb.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Robin Elfrink said: > > Hi, > > > I have a system with hardware raid, which has had some hardware troubles. > > The state this machine is in is now: The raid configuration is OK, but > the filesystem somehow broke seriously. If I mount it under FreeBSD 5.4 > (which is wat the system was running at the time) it completely _hangs_ > (not even kernel panic) when accessing certain directories. Under 6.x > not everything is OK, but at least the system does not hang. > > Now the problem is that I lost some directory trees, and I am looking > for ways to see if I recover them. The obvious first step would be fsck, > but the fs is so broken it gives me: > > root@:~# fsck /dev/da0s1f > ** /dev/da0s1f (NO WRITE) > cannot alloc 18446744067446403432 bytes for inphead > > root@:~# df -h /dev/da0s1f > Filesystem Size Used Avail Capacity Mounted on > /dev/da0s1f 64G -58T 58T -100219% /var/disk > > Google did not help much, has anybody any clue to how I can get fsck to > run properly? Have you tried using fsck_ffs and specifying an alternate superblock? (say 160) 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?62208.10.20.200.100.1149598242.squirrel>