public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Niehusmann <jan@gondor.com>
To: linux-kernel@vger.kernel.org
Subject: uncorrectable ext2 errors
Date: Wed, 6 Aug 2003 17:03:35 +0200	[thread overview]
Message-ID: <20030806150335.GA5430@gondor.com> (raw)

Hi!

A few days ago, I reported some problems with a ext2 filesystem which I
cannot repair with e2fsck. Now I got some new observations.

To summarize the problem: e2fsck reports block bitmap differences, but
telling it to repair these doesn't help, another e2fsck run reports the
same differences.

Now I took a copy of the metadata with e2image -r, and ran e2fsck on
that. Surprisingly, now e2fsck was able to repair the differences.

With this corrected filesystem, I took a look at what e2fsck did change
on the filesystem. Interestingly, the errors are very systematic. It's
mainly sequences of 4096 bytes which should be all 255, but are
3,0,0,0,300,7,0,... (rest are 0s). These blocks start at the following 
positions:

6630000001
6638000001
6640000001
6648000001
6748000001
6750000001
6758000001
6760000001
6768000001
6790000001
6798000001
67A0000001
67A8000001
67B0000001
67B8000001
67C0000001
67C8000001
67D0000001
67D8000001
67E0000001
67E8000001

To me, this looks like some strange problem in a layer below the
filesystem. So it may be LVM, ide, promise ide driver, or a hardware
fault.

Do you have any idea how to further diagnose this?

Jan


             reply	other threads:[~2003-08-06 15:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 15:03 Jan Niehusmann [this message]
2003-08-06 17:06 ` uncorrectable ext2 errors Andreas Dilger
2003-08-06 18:38   ` Jan Niehusmann
2003-08-06 18:52     ` Mike Fedyk
2003-08-06 19:50 ` Jan Niehusmann
2003-08-07 11:06 ` Jan Niehusmann
2003-08-07 12:27   ` LBA48 on Promise 20265 Jan Niehusmann
2003-08-07 21:12   ` uncorrectable ext2 errors Andries Brouwer
2003-08-10 20:55     ` Jan Niehusmann
2003-08-10 21:19       ` Andries Brouwer
2003-08-10 21:34         ` Jan Niehusmann
2003-08-10 21:58           ` Andries Brouwer
2003-08-10 22:10             ` Jan Niehusmann
2003-08-10 22:33               ` IDE bug - was: " Andries Brouwer
2003-08-12 15:36                 ` Alan Cox
2003-08-12 16:32                   ` Bartlomiej Zolnierkiewicz
2003-08-12 22:50                   ` Andries Brouwer
2003-08-13  0:21                     ` Bartlomiej Zolnierkiewicz
2003-08-13  8:03                       ` Jan Niehusmann
2003-08-13  9:25                         ` Jan Niehusmann
2003-08-13 11:16                         ` Alan Cox
2003-08-13 11:20                           ` Jan Niehusmann
2003-08-13 12:12                             ` Jan Niehusmann
2003-08-13 16:31                           ` Jan Niehusmann
2003-08-13 18:38                             ` Alan Cox
2003-08-13 12:21                         ` Bartlomiej Zolnierkiewicz
2003-08-13 13:27                       ` Andries Brouwer
2003-08-13 22:05                         ` Jan Niehusmann
2003-08-13 22:32                           ` Bartlomiej Zolnierkiewicz
2003-08-13 22:36                       ` Jan Niehusmann
2003-08-13 23:14                         ` Bartlomiej Zolnierkiewicz
2003-08-14  6:37                           ` Jan Niehusmann
2003-08-10 23:01           ` Bartlomiej Zolnierkiewicz

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=20030806150335.GA5430@gondor.com \
    --to=jan@gondor.com \
    --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