Date: Tue, 6 Jun 2006 10:28:35 -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: <49874.10.20.200.100.1149607715.squirrel@10.20.200.100> In-Reply-To: <44859643.6030005@introweb.nl> References: <44852CF1.5070300@introweb.nl> <62208.10.20.200.100.1149598242.squirrel@10.20.200.100> <44857BA4.90405@introweb.nl> <56782.10.20.200.100.1149599550.squirrel@10.20.200.100> <44859643.6030005@introweb.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Robin Elfrink said: > Eric Anderson wrote: > >> 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? > > I have no experience with fsdb, so that will take some time for me to > read the manuals. > > The filesystem was mounted read-only just then, but fsck_uff -b 160 > /dev/da0s1f only says it copies the block, and leaves the filesystem > dirty. > > root@:~# fsck_ffs -b 160 /dev/da0s1f > Alternate super block location: 160 > ** /dev/da0s1f > cannot alloc 188446744067446403432 bytes for inphead > > UPDATE STANDART SUPERBLOCK? [yn] y > > > ***** FILE SYSTEM STILL DIRTY ***** > > > I tried with several backup copies (as newfs -N said it would make; this > is a standard install with no fs optimizations). All with the same result. > > > Robin And then after that, you tried the regular: fsck_ffs -y /dev/da0s1f ? 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?49874.10.20.200.100.1149607715.squirrel>