From: Pierre Ossman <pierre-list@ossman.eu>
To: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Strange read data corruption on ext4/LVM/md
Date: Thu, 20 May 2010 09:14:29 +0200 [thread overview]
Message-ID: <20100520091429.192d560c@mjolnir.ossman.eu> (raw)
In-Reply-To: <20100519233408.7436bd9b@mjolnir.ossman.eu>
[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]
(adding linux-ide)
On Wed, 19 May 2010 23:34:08 +0200
Pierre Ossman <pierre@ossman.eu> wrote:
>
> I'm mostly talking to myself at this point, but one thing that occurs
> to me here is 4096 sectors line up decently with the numbers above.
> 0x380 is just at the end of a 512 byte sector, and 0xf80 is just at the
> end of a 4096 byte one. Not sure it's relevant, but then again I've
> stayed blissfully unaware of how this sector size transformation is
> going to happen. :)
>
Ignore the above. Math is hard.
I did some more testing though, and this might be a low level issue. I
did the following multiple times:
# dd if=/dev/sde skip=4k bs=4M count=500 | md5sum
And the results were:
13aa29adcd16f8d0faf3cb5c39f43826
d1e3df33c0b0d03c61f880a8f2bb6cfb
13aa29adcd16f8d0faf3cb5c39f43826
13aa29adcd16f8d0faf3cb5c39f43826
13aa29adcd16f8d0faf3cb5c39f43826
13aa29adcd16f8d0faf3cb5c39f43826
7a746328b60a63b76847c3e1319a8534
13aa29adcd16f8d0faf3cb5c39f43826
Note that this is a live system, so there is some chance that something
wrote to than area, then restored it to the previous state. I'm not
sure how likely that is.
If not, then it would seem that this is a problem in either the disks,
the controller or the controller driver. The components are WD
WD1002FAEX, sil3132 and sata_sil24 respectively.
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by FRA, a
Swedish intelligence agency. Make sure your server uses
encryption for SMTP traffic and consider using PGP for
end-to-end encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next parent reply other threads:[~2010-05-20 7:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100519225653.1fedb453@mjolnir.ossman.eu>
[not found] ` <20100519230426.47c6c1ed@mjolnir.ossman.eu>
[not found] ` <20100519232906.3be82279@mjolnir.ossman.eu>
[not found] ` <20100519233408.7436bd9b@mjolnir.ossman.eu>
2010-05-20 7:14 ` Pierre Ossman [this message]
2010-05-20 8:57 ` Strange read data corruption on ext4/LVM/md Tejun Heo
2010-05-20 9:29 ` Pierre Ossman
2010-05-20 9:42 ` Tejun Heo
2010-05-20 10:22 ` Pierre Ossman
2010-05-20 14:00 ` Pierre Ossman
2010-05-20 16:28 ` Pierre Ossman
2010-07-15 19:38 ` Pierre Ossman
2011-01-16 14:01 ` Pierre Ossman
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=20100520091429.192d560c@mjolnir.ossman.eu \
--to=pierre-list@ossman.eu \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).