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 structure Pass 3: Checking directory connectivity 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 maybe the solution is to say NO to the above question from fsck, then manually removing lost+found, creating a new one, and fscking again. Of course I don't take responsibility for this.
christian.