From: Marc MERLIN <marc@merlins.org>
To: Sander <sander@humilis.net>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Need help mounting laptop corrupted root btrfs. Kernel BUG at fs/btrfs/volumes.c:3707 - FIXED
Date: Wed, 31 Oct 2012 08:40:56 -0700 [thread overview]
Message-ID: <20121031154056.GE3290@merlins.org> (raw)
In-Reply-To: <20121031092440.GA31209@panda>
On Wed, Oct 31, 2012 at 10:24:40AM +0100, Sander wrote:
> Marc MERLIN wrote (ao):
> > What happened is that my SSD is craping out and failing to write after
> > a certain number of uptime hours.
>
> What model ssd is that if I may ask?
I had my first one, Crucial C300 just die with all my data about 3 months
later.
I spent 2-3 weeks trying to get acceptable performance (i.e. faster than a
HD) off 2 samsung 830s (you might remember some spam from me here about them
when I thought it might be an issue with btrfs initially).
Now, I have an OCZ Vertex 4.
That said, it's working fine again for now after I went back to kernel 3.5.3
(down from 3.6.3). It hasn't been long enough to say for sure, but there is
a remote possibility that changes in 3.6 actually caused my drive to freeze
after several hours of use.
When that happened (3 times), 2 of those times, btrfs did not manage to
write all its data before access was cutoff, and I got the bug I reported
here, which in turn crashes any kernel you try to mount the FS with.
Cleaning the log manually fixed it both times so far.
For now, I'll stick with 3.5.3 for a while to make sure my drive is actually
ok (it seems to be afterall), and once I'm happy that it's the case, I'll go
back to 3.6.3 with serial console remote logging and try to capture the full
sata failure I got with 3.6.3.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2012-10-31 15:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 19:58 Need help mounting laptop corrupted root btrfs. Kernel BUG at fs/btrfs/volumes.c:3707 Marc MERLIN
2012-10-25 20:03 ` cwillu
2012-10-25 20:12 ` Marc MERLIN
2012-10-29 4:30 ` Marc MERLIN
2012-10-29 5:05 ` Chris Murphy
2012-10-29 17:42 ` Marc MERLIN
2012-10-29 17:48 ` Need help mounting laptop corrupted root btrfs. Kernel BUG at fs/btrfs/volumes.c:3707 - FIXED Marc MERLIN
2012-10-30 15:46 ` Marc MERLIN
2012-10-31 9:24 ` Sander
2012-10-31 15:40 ` Marc MERLIN [this message]
2012-11-01 10:56 ` Sander
2012-11-01 16:16 ` Marc MERLIN
2012-10-26 18:29 ` Need help mounting laptop corrupted root btrfs. Kernel BUG at fs/btrfs/volumes.c:3707 Marc MERLIN
[not found] <E1TTCzR-0001nz-1p@gandalfthegreat.merlins.org>
[not found] ` <20121030144914.GA18659@merlins.org>
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=20121031154056.GE3290@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=sander@humilis.net \
/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;
as well as URLs for NNTP newsgroup(s).