Skip to contentSkip to conversation

Corrupt ext2/ext3 directory entries not recovered by e2fsck

DISCUSSION Manfred Spraul 3 participants 4 messages Oct 13, 2001 – Oct 14, 2001

lore
Share & tools
lore
#0 lore raw

Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Quoted 11 lines

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?

One of my broken harddisks showed similar behaviour:
* write operations succeeded.
* read operations immediately after the write (write 16 MB including the damaged sector, then read all 16 MB) sometimes succeeded.
* read operations after 5 minutes always failed.

--
Manfred

#1 lore raw
Quoted 11 lines · Manfred Spraul
Quoted 11 lines

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.

Quoted 2 lines

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.

#2 lore raw
Quoted 13 lines · Keith Owens
Quoted 11 lines · Manfred Spraul
Quoted 11 lines

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.

Quoted 7 lines
Quoted 2 lines

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.."

#3 lore raw
Quoted 2 lines · Oliver Xymoron

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

It is root. The problem exists on 2.4.9 kernels as well as 2.4.13-pre1. The 2.4.9 kernels are RH 7.2 IA64 beta so they might contain code from the -ac tree.