From: Roman Mamedov <rm@romanrm.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Marat Khalili <mkh@rqc.ru>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Backing up BTRFS metadata
Date: Fri, 12 May 2017 00:22:00 +0500 [thread overview]
Message-ID: <20170512002200.73d5207f@natsu> (raw)
In-Reply-To: <CAJCQCtTbE6M23e8EmB23pp89Y8673BeY+p_tkox3orY-AS2DJQ@mail.gmail.com>
On Thu, 11 May 2017 09:19:28 -0600
Chris Murphy <lists@colorremedies.com> wrote:
> On Thu, May 11, 2017 at 8:56 AM, Marat Khalili <mkh@rqc.ru> wrote:
> > Sorry if question sounds unorthodox, Is there some simple way to read (and
> > backup) all BTRFS metadata from volume?
>
> btrfs-image
Hm, I thought that's for debugging only, and that you can't actually restore
metadata onto a data-containing FS and have anything mountable/readable as a
result.
Seems not to be the case, and in fact, could this be one of the "missing
links" in the Fsck story,
-w
Walk all the trees manually and copy any blocks that are
referenced. Use this option if your extent tree is corrupted to
make sure that all of the metadata is captured.
This certainly does sound like something to try for some of those broken
filesystems where Btrfsck refuses to do anything. Save image with this manual
walking/reconstruction of the trees, then restore. Too bad I already nuked
mine, so can't experiment with that.
--
With respect,
Roman
next prev parent reply other threads:[~2017-05-11 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 14:56 Backing up BTRFS metadata Marat Khalili
2017-05-11 15:19 ` Chris Murphy
2017-05-11 15:23 ` Marat Khalili
2017-05-11 19:22 ` Roman Mamedov [this message]
2017-05-11 19:37 ` Hugo Mills
2017-05-12 6:06 ` Marat Khalili
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=20170512002200.73d5207f@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=mkh@rqc.ru \
/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