mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Corrupt ext2/ext3 directory entries not recovered by e2fsck
Date: Sat, 13 Oct 2001 16:06:35 +0200	[thread overview]
Message-ID: <3BC84A6B.C788C477@colorfullife.com> (raw)

 
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

             reply	other threads:[~2001-10-13 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-13 14:06 Manfred Spraul [this message]
2001-10-13 15:02 ` Keith Owens
2001-10-13 19:09   ` Oliver Xymoron
2001-10-14  1:15     ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2001-10-13 12:44 Keith Owens
2001-10-13 12:59 ` Keith Owens
2001-10-13 19:46 ` Bernd Eckenfels

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BC84A6B.C788C477@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®