From: sri <toyours_sridhar@yahoo.co.in>
To: linux-btrfs@vger.kernel.org
Subject: recreate subvolume (not using btrfs send and receive)
Date: Fri, 10 Apr 2015 06:50:34 +0000 (UTC) [thread overview]
Message-ID: <loom.20150410T084317-180@post.gmane.org> (raw)
Hi,
I looking for a way to collect all metadata and data blocks associated
with a subvolume or entire btrfs and recreate the same by dumping all
blocks on newly allocated disks and bring the file system back assuming
same number of disks are provided.
Example is say for ext3/ext4 using the information of used block bit map
information in each block group, I can Identify all used blocks of the
ext3/ext4 partition and simply copy all blocks.
Above will contains all metadata + data blocks (only used)
For a 10 Gb disk and say only 2 gb is used, using above, I can collect all
2bg blocks.
Thank I can simply dump those blocks to a destination partition and
recreate the partition.
In the same way I am looking something similar for btrfs.
Could anybody let me know is there a way to do this or something similar I
can work it out.
Thanks you.
reply other threads:[~2015-04-10 7:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=loom.20150410T084317-180@post.gmane.org \
--to=toyours_sridhar@yahoo.co.in \
--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).