Messages in this thread |  | | Date | Sat, 13 Oct 2001 14:09:32 -0500 (CDT) | From | Oliver Xymoron <> | Subject | Re: Corrupt ext2/ext3 directory entries not recovered by e2fsck |
| |
On Sun, 14 Oct 2001, Keith Owens wrote:
> On Sat, 13 Oct 2001 16:06:35 +0200, > Manfred Spraul <manfred@colorfullife.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.
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.."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |