From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Need help mounting laptop corrupted root btrfs. Kernel BUG at fs/btrfs/volumes.c:3707
Date: Sun, 28 Oct 2012 21:30:02 -0700 [thread overview]
Message-ID: <20121029043002.GA8019@merlins.org> (raw)
In-Reply-To: <20121025201223.GB24111@merlins.org>
On Thu, Oct 25, 2012 at 01:12:23PM -0700, Marc MERLIN wrote:
> On Thu, Oct 25, 2012 at 02:03:49PM -0600, cwillu wrote:
> > > 3) Want me to try btrfsck although it may make it impossible for me to
> > > reproduce the bug and test a fix, as well as potentially break the filesystem
> > > more (last time I tried btrfsck, it outputted thousands of lines and never converged
> > > to a state it was happy with)
> >
> > This looks like something btrfs-zero-log would work around (although
> > -o recovery should do mostly the same things). That would destroy the
> > evidence though, and may just make things (slightly) worse, so I'd
> > wait to see if anyone suggests something better before trying it. If
> > you're ultimately ending up restoring from backup though, it may save
> > you that effort at least.
>
> Thanks for pointing out btrfs-zero-log, I hadn't re-read the wiki page since
> this got added.
> But I'll hold off at least until tomorrow morning (GMT-7).
I'm a bit surprised that no one seems to be replying on btrfs crashes,
that's a bit worrisome. I'm willing to risk my data somewhat, but if finding
a problem doesn't help fixing the code, I'm not sure if I'm helping anymore
:-/
Since I ran out of time, I tried:
gandalfthegreat:~# btrfs-zero-log
usage: btrfs-zero-log dev
Btrfs Btrfs v0.19
gandalfthegreat:~# btrfs-zero-log /dev/mapper/bootdsk
Check tree block failed, want=7533391872, have=17347973115472321934
Check tree block failed, want=7533391872, have=17347973115472321934
Check tree block failed, want=7533391872, have=8450612919225897562
Check tree block failed, want=7533391872, have=17347973115472321934
Check tree block failed, want=7533391872, have=17347973115472321934
read block failed check_tree_block
gandalfthegreat:~#
So from here, unless someone chimes in tomorrow, I'm going to have to wipe
my filesystem and start over. I suppose that means btrfs can likely still
cause unknown and unfixable corruption.
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-29 4:30 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 [this message]
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
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=20121029043002.GA8019@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).