From: Chris Mason <chris.mason@oracle.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Dave Airlie <airlied@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: SSD + sata_nv + btrfs oops
Date: Tue, 1 Jun 2010 07:23:42 -0400 [thread overview]
Message-ID: <20100601112342.GC8980@think> (raw)
In-Reply-To: <4C049C6A.8060605@garzik.org>
On Tue, Jun 01, 2010 at 01:36:42AM -0400, Jeff Garzik wrote:
> 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.
Correct, we do pretty well when there is an alternate copy but we're
still working on the eios when there is only one.
Dave, one the hardware side is sorted out, if you have trouble with the
btrfs data let me know.
-chris
next prev parent reply other threads:[~2010-06-01 11:25 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
2010-06-01 11:23 ` Chris Mason [this message]
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=20100601112342.GC8980@think \
--to=chris.mason@oracle.com \
--cc=airlied@gmail.com \
--cc=jeff@garzik.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