Re: Corrupt ext2/ext3 directory entries not recovered by e2fsck
Keith Owens (firstname.lastname@example.org)
Sun, 14 Oct 2001 01:02:33 +1000
On Sat, 13 Oct 2001 16:06:35 +0200,
Manfred Spraul <email@example.com> wrote:
>> I forgot to mention that both fsck.ext2 and fsck.ext3 report
>> 1: Entry 'sendmail.pid' in /var/run (686849) has
>> deleted/unused inode 688415. CLEARED.
>> /1: Entry 'crond.pid' in /var/run (686849) has
>> deleted/unused inode 688416. CLEARED.
>> /1: Entry 'xfs.pid' in /var/run (686849) has
>> deleted/unused inode 688417. CLEARED.
>> /1: Entry 'atd.pid' in /var/run (686849) has
>> deleted/unused inode 688418. CLEARED.
>All inodes are in the same sector.
>Could you try out if that sector is destroyed?
It should not matter which sector the inode is in, the directory entry
should have been cleared, independent of the inode. But I checked
anyway, dd of the entire partition to /dev/null succeeded, no disk
error messages anywhere in the logs at any time.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/