All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Need help mounting laptop corrupted root btrfs. Kernel BUG at fs/btrfs/volumes.c:3707
Date: Thu, 25 Oct 2012 13:12:23 -0700	[thread overview]
Message-ID: <20121025201223.GB24111@merlins.org> (raw)
In-Reply-To: <CAE5mzvi=y6Auyr9cGMOm=tUSSj7sSQ78W0Bnzk+dJOqkW6z6jA@mail.gmail.com>

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).

If someone would like me to hold off a bit longer, please let me know and
I'll wait for whatever patch you'd like me to try.

As for backups, yes, I have some :) and I also have hourly, daily, weekly
btrfs subvolume snapshots, but I can't use those currently since I can't
mount the base filesystem.
If my latest snapshot is corrupted, once I know which subvolume has the
problem (I can't quite tell since the crash doesn't say which subvolume is
causing it), I can revert to the last hourly snapshot.

Thanks for your reply.
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/  

  reply	other threads:[~2012-10-25 20:12 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 [this message]
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
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>

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=20121025201223.GB24111@merlins.org \
    --to=marc@merlins.org \
    --cc=cwillu@cwillu.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.