lkml.org 
[lkml]   [2001]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Corrupt ext2/ext3 directory entries not recovered by e2fsck

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

> 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
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:08    [W:0.038 / U:0.396 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site