On Thursday 15 September 2005 15:33, Manuel Bouyer wrote:
> On Thu, Sep 15, 2005 at 05:02:52PM -0400, Chris Tribo wrote:
> > Perhaps you have a kernel with 64-bit inodes and userland fsck tools
> > that is only expecting 32-bit inodes?
>
> I think there is a more serious problem:
> > [...]
> >
> > >** Phase 2 - Check Pathnames
> > >fsck_ffs: inoinfo: inumber 578090778291601410 out of range
>
> # printf %x\\n 578090778291601410
> 805ca8000000002
>
> This number is 64bit, with garbage in the highter numbers.

32-bit inode file system that fsck thinks is 64-bit?