Re: Corrupt ext2/ext3 directory entries not recovered by e2fsck

[Oliver Xymoron]

On Sun, 14 Oct 2001, Keith Owens wrote:

> On Sat, 13 Oct 2001 16:06:35 +0200,
> Manfred Spraul <[e-mail]> 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.

Is this your root partition perhaps? Fsck of a mounted device might act a
little differently with the new blockdev-in-pagecache approach.

--
 "Love the dolphins," she advised him. "Write by W.A.S.T.E.."