From: Jeff Garzik <jeff@garzik.org>
To: Dave Airlie <airlied@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: SSD + sata_nv + btrfs oops
Date: Tue, 01 Jun 2010 01:36:42 -0400 [thread overview]
Message-ID: <4C049C6A.8060605@garzik.org> (raw)
In-Reply-To: <AANLkTilqsIdlzZgUf7TMLHYKqHDZoVkcs42vcG8wXKEr@mail.gmail.com>
On 05/31/2010 11:04 PM, Dave Airlie wrote:
> Hi guys,
>
> I've been running an Intel SSD (the KS one) on my Dell XPS710 desktop
> machine, with btrfs on it.
>
> I'm not sure the btrfs oops isn't due to the disk/controller doing
> something bad (almost guaranteed).
The btrfs oops may be poor handling of an I/O error thrown by the block
error.
Root cause is definitely your SATA PHY throwing some hardware errors
from the transport layer (low level SATA packet transmission failures).
Everything else sorta falls apart after that.
First guesses are the usual suspects: cabling, temperature, power or
SATA ports on the [SATA controller | SATA device] going bad.
Disabling swncq will only improve things from the perspective of slowing
things down and giving the hardware less to do. swncq makes things
parallel, so forcing only one transaction at a time certainly increases
the chances of success by reducing complexity and serializing transactions.
Jeff
next prev parent reply other threads:[~2010-06-01 5:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 3:04 SSD + sata_nv + btrfs oops Dave Airlie
2010-06-01 4:59 ` Robert Hancock
2010-06-01 5:02 ` Dave Airlie
2010-06-01 5:06 ` Robert Hancock
2010-06-01 5:36 ` Jeff Garzik [this message]
2010-06-01 11:23 ` Chris Mason
2010-06-08 19:24 ` Maciej Rutecki
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=4C049C6A.8060605@garzik.org \
--to=jeff@garzik.org \
--cc=airlied@gmail.com \
--cc=chris.mason@oracle.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