mingo,
Thank you very much for your help.
I now recovered almost all data. No need to recreate the raid
array, or the ext2 filesystem.
The program, e2fsck, is good. It recovered the filesystem
successfully. I answered "no" on its question:
Clone duplicate/bad blocks? No
^^^^
After that, e2fsck asked me if I want to delete the inode.
I answered Yes to the second question, and all goes smoothly.
By the way, I need one more help. The /dev/md0 partition has a lot
of entries in its lost+found directory even after "rm -f". It has
9484 entries now. When I tried rm, it says "Operation not permited".
The programs "lsattr" and "chattr" did not help me. "ls -l" shows
some of them are devices files, pipes ... All strange file modes. :-(
Therefore, I tried "mklost+found", but it complained there is already
one. I renamed the lost+found to lost+found.OLD and used
"mklost+found" again to make an empty lost+found.
I wish that I can "rm -rf lost+found.OLD"
--
sysuh
On Tue, Sep 07, 1999 at 06:29:21PM +0200, [EMAIL PROTECTED] wrote:
...
>> e2fsck 1.15, 18-Jul-1999 for EXT2 FS 0.5b, 95/08/09
>> Pass 1: Checking inodes, blocks, and sizes
>> Duplicate blocks found... invoking duplicate block passes.
>> Pass 1B: Rescan for duplicate/bad blocks
>> Duplicate/bad block(s) in inode 135841: 47 47 47
>> Pass 1C: Scan directories for inodes with dup blocks.
>> Pass 1D: Reconciling duplicate blocks
>
> this indeed seems to be an (RAID-unrelated) e2fsck problem, Ted, Stephen,
> any ideas?
