problems with fsck and 5.3

[Lowell Gilbert]

Felipe Garcia <felipe at garcia-lind.com> writes:

> fsck fails, is there any way to save this fs.. force it to be marked
> ok or is there a fix for fsck (tired with the lastest version out of
> cvs does the same)
> 
> 
> ** /dev/amrd1e (NO WRITE)
> ** Last Mounted on /usr/local/media
> ** Phase 1 - Check Blocks and Sizes
> INCORRECT BLOCK COUNT I=6526350 (180224 should be 113760)
> CORRECT? no
> 
> INCORRECT BLOCK COUNT I=6526354 (83552 should be 65984)
> CORRECT? no
> 
> INCORRECT BLOCK COUNT I=6526356 (81504 should be 65984)
> CORRECT? no
> 
> fsck_ffs: cannot alloc 3400404768 bytes for inoinfo

That's a huge amount of memory, all right.  A quick look at the code
makes me think that it might be a word-size error; are you running on
a 64-bit platform by any chance?

This is probably worth a PR, and definitely worth a message to the
filesystem experts.