drive failure, now 'cannot alloc 494581644 bytes for inoinfo' and 'bad inode number 3556352 to nextinode'

Doug White dwhite at
Thu Apr 8 14:45:48 PDT 2004

On Tue, 6 Apr 2004, Will Saxon wrote:

> > I can pretty much assure you the volume isn't OK. The types of errors
> > you're seeing are indicative of severe corruption, usually
> > due to random
> > data being written over critical filesystem blocks.  I'd
> > 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.
> >
> 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.

No, since its a function of your RAID controller.  FreeBSD just sees one
opaque volume.

You may wish to consider a more robust RAID controller :)

Doug White                    |  FreeBSD: The Power to Serve
dwhite at          |

More information about the freebsd-current mailing list