All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Pierre Ossman <pierre-list@ossman.eu>
Cc: 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 10:57:29 +0200	[thread overview]
Message-ID: <4BF4F979.4070903@kernel.org> (raw)
In-Reply-To: <20100520091429.192d560c@mjolnir.ossman.eu>

On 05/20/2010 09:14 AM, Pierre Ossman wrote:
> 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.

There is a report that sil3124/32 recognizes FIS corruption but keeps
using the payload anyway thus leading to data corruption when the bus
condition on pci-e side isn't ideal.  Does moving the controller to
different slot make difference?

Thanks.

-- 
tejun

  reply	other threads:[~2010-05-20  8:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 20:56 Strange read data corruption on ext4/LVM/md Pierre Ossman
2010-05-19 21:04 ` Pierre Ossman
2010-05-19 21:29   ` Pierre Ossman
2010-05-19 21:34     ` Pierre Ossman
2010-05-20  7:14       ` Pierre Ossman
2010-05-20  8:57         ` Tejun Heo [this message]
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
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=4BF4F979.4070903@kernel.org \
    --to=tj@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-list@ossman.eu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.