From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Problem with unmountable filesystem.
Date: Wed, 17 Sep 2014 20:07:34 +0000 (UTC) [thread overview]
Message-ID: <pan$7ad6e$263e56a5$f2bf0e6d$c264643b@cox.net> (raw)
In-Reply-To: 22B49628-3659-4D83-BE99-A173CAFF23F9@colorremedies.com
Chris Murphy posted on Wed, 17 Sep 2014 12:57:59 -0600 as excerpted:
> But I think you're onto something, that a good superblock can point to a
> corrupt tree root, and then not have a straight forward way to mount the
> good tree root. If I understand this correctly.
This is what I ran into myself a couple months ago.
I ended up doing a restore as the simplest recovery I could do, then
recreated the affected filesystems. It happened on two filesystems
(separate, I don't trust subvolumes precisely because it's the same
filesystem underneath and that's too many eggs in one basket for my
comfort), /var/log and /home. I was able to restore nearly all of /home
(enough that I wasn't aware of anything missing except symlinks that
restore doesn't work with), but lost about half of /var/log, which I did
first and made a couple mistakes on that I didn't repeat on /home.
I figured there was a way to fix the filesystems as they were, but these
threads about deliberately corrupting the first superblock in ordered to
use the others hadn't appeared yet, and between restore and backups I got
enough back not to be worried about the rest, so restore was "good
enough".
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-09-17 20:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 14:40 Problem with unmountable filesystem Austin S Hemmelgarn
2014-09-16 20:57 ` Chris Murphy
2014-09-17 11:23 ` Austin S Hemmelgarn
2014-09-17 18:57 ` Chris Murphy
2014-09-17 20:07 ` Duncan [this message]
2014-09-18 17:12 ` Austin S Hemmelgarn
2014-09-18 21:15 ` Chris Murphy
2014-09-18 21:25 ` Duncan
2014-09-19 17:07 ` Chris Murphy
2014-09-19 17:42 ` Austin S Hemmelgarn
2014-09-17 20:22 ` Duncan
2014-09-18 17:19 ` Austin S Hemmelgarn
2014-09-19 17:54 ` Chris Murphy
2014-09-19 18:44 ` Austin S Hemmelgarn
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='pan$7ad6e$263e56a5$f2bf0e6d$c264643b@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).