mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
	Andy Whitcroft <apw@canonical.com>
Subject: Re: Some hints needed how to handle SATA ALPM failures
Date: Fri, 18 Feb 2011 15:50:57 +0100	[thread overview]
Message-ID: <20110218145057.GM21209@htj.dyndns.org> (raw)
In-Reply-To: <4D5E6CE1.9020908@canonical.com>

Hello,

On Fri, Feb 18, 2011 at 01:58:09PM +0100, Stefan Bader wrote:
> We are hoping that those working more closely with the SATA code might
> be aware of this issue.  As the symptoms are so severe (data corruption)
> we have ALPM disabled globally, but this does make it hard to get more
> targeted information on affected platforms.

What do you mean by data corruption?  File system ro remount or actual
fs corruption?  If actual fs corruption is happening, it's highly
likely that there's an underlying issue with the hardware.  If data
corruption can be reproduced, can you please run smartctl -a before
and after such failure and post the outputs?

As for ro remounts, I recall applying fixes for that months ago.  I
don't remember the details but some configurations raised extra PHY
event afterwards and command was failed without retry.  Anyways, it
got fixed.  Please dig through the log for details.

Also, the whole LPM thing got revamped several releases ago.  Can you
please test how the recent kernels behave?  There will be failures as
not all hardware can handle LPM well but those failures shouldn't lead
to any catastrophic failures like ro remounting of filesystem.

Thanks.

-- 
tejun

  reply	other threads:[~2011-02-18 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 12:58 Stefan Bader
2011-02-18 14:50 ` Tejun Heo [this message]
2011-02-18 15:55   ` Stefan Bader
2011-02-18 16:16     ` Tejun Heo
2011-02-18 16:51       ` Stefan Bader
2011-03-11 10:27         ` Stefan Bader
2011-03-11 11:01           ` Tejun Heo
2011-03-15 18:02             ` Stefan Bader

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=20110218145057.GM21209@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=apw@canonical.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan.bader@canonical.com \
    /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®