> >Unconnected directory inode 11 (???)
>
> The problem probably is, that on most of my ext2 filesystems
> lost+found *is inode 11*. That means that e2fsck is probably trying
> to move lost+found to itself.
>
> However I have also ext2 filesystems with lost+found being other
> inode numbers. So may
You have a hosed root directory and/or inode. You should say 'no'
to these questions and see if that gets you past the problem.
Barring that there is debugfs that I once used back in the 2.0
kernel days to fix an obnoxious problem like this, turned out the
corruption was very minor, but the fsck
At 11:07 Uhr -0700 5.7.2001, Peter Canning wrote:
I've recently encountered some strange file system corruption problems.
Here's the results of running e2fsck
# e2fsck -f -b 40961 /dev/sdb6
e2fsck 1.21-WIP, 14-Jun-2001 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Pass 2:
: Checking directory connectivity
Unconnected directory inode 11 (???)
Connect to /lost+found? yes
Error while trying to find /lost+found: EXT2 directory corrupted
/lost+found not found. Create? yes
Error creating /lost+found directory (ext2fs_link): EXT2 directory
corrupted
/dev/sdb6: * FILE
4 matches
Mail list logo
