From owner-freebsd-current@FreeBSD.ORG Tue Apr 6 19:11:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 691A616A4CE for ; Tue, 6 Apr 2004 19:11:35 -0700 (PDT) Received: from bragi.housing.ufl.edu (bragi.housing.ufl.edu [128.227.47.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2105E43D39 for ; Tue, 6 Apr 2004 19:11:35 -0700 (PDT) (envelope-from WillS@housing.ufl.edu) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable x-mimeole: Produced By Microsoft Exchange V6.0.6249.0 Date: Tue, 6 Apr 2004 22:10:14 -0400 Message-ID: <0E972CEE334BFE4291CD07E056C76ED802E86938@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: drive failure, now 'cannot alloc 494581644 bytes for inoinfo' and 'bad inode number 3556352 to nextinode' Thread-Index: AcQcQuXtZbVldSksTJiYwR71FJbWRwAAi7sw From: "Will Saxon" To: "Doug White" cc: current@freebsd.org Subject: RE: drive failure, now 'cannot alloc 494581644 bytes for inoinfo' and 'bad inode number 3556352 to nextinode' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Apr 2004 02:11:35 -0000 > -----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