Date: Tue, 06 Jun 2006 16:50:43 +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: <44859643.6030005@introweb.nl> In-Reply-To: <56782.10.20.200.100.1149599550.squirrel@10.20.200.100> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44859643.6030005>