From: Chris Mason <chris.mason@oracle.com>
To: Dave Airlie <airlied@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: btrfs oops on dodgy SSD
Date: Wed, 6 Oct 2010 11:15:26 -0400 [thread overview]
Message-ID: <20101006151526.GP9759@think> (raw)
In-Reply-To: <AANLkTiknCR6Z2=L9FoA8+m7o8dw6=Hq1QHWKn7Oyf9UF@mail.gmail.com>
On Wed, Oct 06, 2010 at 11:07:10AM +1000, Dave Airlie wrote:
> I have an SSD which I use for scratch builds and stuff, it seems to be
> broken or just dislike my NV sata controller.
>
> Was just running Linus tree and got the attached oops when doing a
> kernel build on it this morning.
>
> oops didn't come out in logs, though there were some disk reset and a
> hung task detect.
>
> Might help btrfs robustness maybe if we could avoid the panic ;-)
Ouch, the oops was in the code printing a corrupted btree block. I
should be able to easily trigger this at home...
-chris
next prev parent reply other threads:[~2010-10-06 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 1:07 btrfs oops on dodgy SSD Dave Airlie
2010-10-06 15:15 ` Chris Mason [this message]
2010-10-07 1:39 ` Li Zefan
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=20101006151526.GP9759@think \
--to=chris.mason@oracle.com \
--cc=airlied@gmail.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