Subject: Re: FSCK fails after a crash
To: Manuel Bouyer <bouyer@antioche.eu.org>
From: Steven M. Bellovin <smb@cs.columbia.edu>
List: current-users
Date: 09/15/2005 18:35:54
In message <20050915213328.GA1106@antioche.eu.org>, Manuel Bouyer writes:
>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.
>
Right. And fsck should be able to handle it no matter what, I would
think.
--Steven M. Bellovin, http://www.cs.columbia.edu/~smb