linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Skylar Burtenshaw <daninfuchs@gmail.com>
Subject: Re: Can't mount, power failure - recoverable?
Date: Fri, 13 Jul 2012 14:23:53 +0200	[thread overview]
Message-ID: <201207131423.54019.Martin@lichtvoll.de> (raw)
In-Reply-To: <loom.20120326T104619-458@post.gmane.org>

Am Montag, 26. März 2012 schrieb Skylar Burtenshaw:
> Fajar A. Nugraha <list <at> fajar.net> writes:
> > Didn't Chris' last response basically say "use kernel 3.2 or newer,
> > mount the fs (possibly with -o ro), and copy the data elsewhere"?
> 
> Why yes, yes it did actually. I appreciate your spotlighting it, just
> in case I somehow managed to miss it, though.
> 
> > Have you done that?
> 
> I have. In fact, in my first message, I stated that in all kernels up
> to present 3.2 kernels, I get several minutes of disk churning, then a
> stack trace. Also present in my messages is the fact that the
> filesystem will not mount, as well as data output from the recovery
> program etc which fail to recognize things in the filesystem that they
> require in order to fix it. Did you have something you wished to
> suggest, in order to help me? If so, I'd gladly listen to any proposed
> ideas.

Since I didn´t found any explicit mention on it:

Did you try btrfs-zero-log on the partition prior to mounting it?

All of my BTRFS will not mount after sudden write interruption cases have 
been solved by it. Except one with a BTRFS RAID 0 with lots of 2 TB drives 
at a time where I didn´t know about btrfs-zero-log. Maybe it would have 
helped there, too.

Of course I could be completely off track and this could be a completely 
different issue.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  parent reply	other threads:[~2012-07-13 12:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17  4:24 Can't mount, power failure - recoverable? Skylar Burtenshaw
2012-03-17  7:51 ` cwillu
2012-03-17 19:06   ` Skylar Burtenshaw
2012-03-18 15:16     ` Chris Mason
2012-03-18 18:49       ` Skylar Burtenshaw
2012-03-19 18:02         ` Chris Mason
2012-03-20  3:06           ` Skylar Burtenshaw
2012-03-26  8:34             ` Skylar Burtenshaw
2012-03-26  8:43               ` Hugo Mills
2012-03-26  8:51                 ` Skylar Burtenshaw
2012-03-26  8:44               ` Fajar A. Nugraha
2012-03-26  8:49                 ` Skylar Burtenshaw
2012-03-26  8:56                   ` Fajar A. Nugraha
2012-07-13 12:23                   ` Martin Steigerwald [this message]
2012-07-13 12:28                     ` Hugo Mills
2012-07-13 14:38                       ` Martin Steigerwald
2012-07-14  1:01                         ` Skylar Burtenshaw
2012-07-15 11:20                           ` Martin Steigerwald
2012-07-15 11:30                           ` Hugo Mills
2012-03-17 10:31 ` Hugo Mills
2012-03-17 19:06   ` Skylar Burtenshaw
2012-03-17 12:18 ` Chris Mason
2012-03-17 19:06   ` Skylar Burtenshaw
2012-07-12  0:47     ` Skylar Burtenshaw

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=201207131423.54019.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=daninfuchs@gmail.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 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).