Date: Sun, 11 Jun 2006 15:01:58 -0500 From: Eric Anderson <anderson@centtech.com> To: Robin Elfrink <elfrink@introweb.nl> Cc: freebsd-fs@freebsd.org Subject: Re: Recovery from disk+fs crash Message-ID: <448C76B6.9050200@centtech.com> In-Reply-To: <4486E0F2.8080809@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> <4486C4DA.6080905@introweb.nl> <4486D193.3000801@centtech.com> <4486E0F2.8080809@introweb.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Robin Elfrink wrote: > Eric Anderson wrote: > >> Can you run dumpfs on it, and put the output somewhere accessible on the >> web? > > Yes, here it is: > > http://eddy.introweb.nl/~robin/dump/ > > File da0s1f.dump is the output from 'dumpfs /dev/da0s1f', dumpfs.core is > the result of dumpfs dumping core. > > > > Robin Robin, I looked at it, and it looks like the reading of cylindar group 185 is the culprit. Without fsdb usable, it's hard to attempt fixing. I think the routine that attempts to alloc memory needs to be tweaked to recognize ridiculous numbers, but I'm not sure the best way to do it - I suppose for this case, one could just truncate at some ceiling to get past it, but that would definitely be the wrong thing to do, and dangerous too most likely. I've cc'ed the -fs list, and bcc'ed the -isp list, since this is a filesystem issue, and more people with fs-foo will be able to chime in. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448C76B6.9050200>