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

> -----Original Message-----
> From: Will Saxon 
> Sent: Tuesday, April 06, 2004 6:50 PM
> To: current_at_freebsd.org
> Subject: drive failure, now 'cannot alloc 494581644 bytes for inoinfo'
> and'bad inode number 3556352 to nextinode'
> 
> At the time of the crash, I was using FreeBSD 5.2.1-RC2, 
> however I have since updated to 5.2.1-RELEASE-p4. The array 
> has 1 partition and 2 slices - one 4GB swap slice and 1 
> 400+GB storage slice. This was being used in a samba pilot 
> and had the softupdates, suiddir, noexec, nodev and acl 
> options enabled.
> 
> Basically, in phase 1 fsck -y complains that it cannot 
> allocate enough bytes for inoinfo, then there are a bunch of 
> the following:
> 
> UNKNOWN FILE TYPE I=#######
> UNEXPECTED SOFT UPDATE INCONSISTENCY
> 
> then finally:
> 
> fsck_4.2bsd: bad inode number 3556352 to nextinode

Also, dumpfs coredumps (dumpfs /dev/da1s1d) in case that
piques anyone's interest.

-Will