On Tue, Apr 29, 2008 at 08:03:45PM +0200, Kai Henningsen wrote:
> Package: e2fsprogs
> Version: 1.40.8-2
> Severity: normal
> File: /sbin/e2fsck
>
> Upgrading e2fsprogs did not help with this problem:
>
> fsck 1.40.8 (13-Mar-2008)
> e2fsck 1.40.8 (13-Mar-2008)
> Backup contains a file system with errors, check forced.
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> '..' in /lost+found/#122068977 (122068977) is <The NULL inode> (0),
> should be /lost+found (11).
> Fix? yes
>
> Couldn't fix parent of inode 122068977: Couldn't find parent directory
> entry
>
Um, that's interesting. What this means is that e2fsck tried to
update the '..' entry of the directory inode #122068977, as part of
removing it to the lost+found directory, but it couldn't because it
couldn't find the '..' entry. But if the '..' entry was missing, it
should have been caught in pass #2. Hmm...
Could you send me the following:
debugfs /dev/sdXX <----- replace /dev/sdXX with the device name of
your filesystem
debugfs: stat <122068977>
...
debugfs: dump <122068977> /tmp/directory-dump
And then send me the output of the "stat <122068977>" command as well
as the /tmp/directory-dump file generated by debugfs?
Many thanks!!
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
