Perhaps you have a kernel with 64-bit inodes and userland fsck tools  
that is only expecting 32-bit inodes?

On Sep 15, 2005, at 4:37 PM, Vincent wrote:

> Yet, there is something strange :
>
> # newfs /dev/wd0g
> /dev/wd0g: 7168.0MB (14680064 sectors) block size 16384, fragment  
> size 2048
>         using 39 cylinder groups of 183.80MB, 11763 blks, 23040  
> inodes.
> super-block backups (for fsck -b #) at:
>        32,   376448,   752864,  1129280,  1505696,  1882112,   
> 2258528,  2634944,
>   3011360,  3387776,  3764192,  4140608,  4517024,  4893440,   
> 5269856,  5646272,
>   6022688,  6399104,  6775520,  7151936,  7528352,  7904768,   
> 8281184,  8657600,
>   9034016,  9410432,  9786848, 10163264, 10539680, 10916096,  
> 11292512, 11668928,
>  12045344, 12421760, 12798176, 13174592, 13551008, 13927424, 14303840,
> # fsck -f /dev/wd0g
> ** /dev/rwd0g
> ** File system is already clean
> ** Last Mounted on
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> fsck_ffs: inoinfo: inumber 578090778291601410 out of range
> #
>
>
> So I guess *there is* something wrong, either with fsck or the  
> kernel or whatever, no?
>
> Vincent
>
> !DSPAM:4329db7c264783376685036!
>