Date: Tue, 6 Apr 2004 22:10:14 -0400 From: "Will Saxon" <WillS@housing.ufl.edu> To: "Doug White" <dwhite@gumbysoft.com> Cc: current@freebsd.org Subject: RE: drive failure, now 'cannot alloc 494581644 bytes for inoinfo' and 'bad inode number 3556352 to nextinode' Message-ID: <0E972CEE334BFE4291CD07E056C76ED802E86938@bragi.housing.ufl.edu>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Doug White [mailto:dwhite@gumbysoft.com] > Sent: Tuesday, April 06, 2004 9:52 PM > To: Will Saxon > Cc: current@freebsd.org > Subject: Re: drive failure, now 'cannot alloc 494581644 bytes for > inoinfo' and 'bad inode number 3556352 to nextinode' >=20 >=20 > I can pretty much assure you the volume isn't OK. The types of errors > you're seeing are indicative of severe corruption, usually=20 > due to random > data being written over critical filesystem blocks. I'd=20 > suggest running a > parity verify against the volume to force corrections to start with -- > this can't make it any worse than it already is, and may recover the > damaged blocks on the disk that lost power. >=20 Is there a freebsd tool that will let me do the parity verify? This controller has the most minimal BIOS interface possible, I think they want all the real work to be done through a windows utility. > You could also try running fsck against an alternate superblock to get > around any corruption thats specific to the primary superblock, but my > experience with this kind of failure has shown that there's=20 > usually more > significant damage than just a mulched superblock. >=20 > Its quite likely that the filesystem is not recoverable. =20 > Hope you have > backups :-) Not quite, but it was 'in testing' anyway. I guess it failed the test! -Will
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0E972CEE334BFE4291CD07E056C76ED802E86938>