From: Stephane Chazelas <stephane_chazelas@yahoo.fr>
To: "krzf83@gmail.com " <krzf83@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: feature request: btrfs-image without zeroing data
Date: Mon, 11 Jul 2011 13:58:26 +0100 [thread overview]
Message-ID: <chaz20110711125826.GA18391@seebyte.com> (raw)
In-Reply-To: <CAJ1PRSnyU5G5_08UtGKvhTQUEOvK+KSYo7WQV06N5Qn8efPXgw@mail.gmail.com>
2011-07-11 14:39:18 +0200, krzf83@gmail.com :
> 2011/7/11 Stephane Chazelas <stephane_chazelas@yahoo.fr>:
[...]
> > See also
> > http://thread.gmane.org/gmane.comp.file-systems.btrfs/9675/focus=9820
> > for a way to transfer btrfs fs.
> >
> > (Add a layer of "copy-on-write" on the original devices (LVM
> > snapshots, nbd/qemu-nbd cow...), "btrfs add" the new device(s)
> > and then "btrfs del" of the cow'ed original devices.
[...]
> Copying on block level (dd, lvm) is old trick, however this takes same
> ammount of time regardless of actual space used in filesystem. Hence
> this feature request. Images inside filesystem can copy only actualy
> used data and metadata, which dramaticly reduces copy times in large
> volumes that are not filled up...
The method I suggest doesn't copy the whole disks, please read
more carefully. It can also work to copy from a 3 disk setup to
a 1 disk setup or the other way round.
With btrfs, you can add devices to a FS dynamically, you can
also delete devices in which case data is being transfered to
the other devices. The method I suggest uses that feature.
Cheers,
Stephane
prev parent reply other threads:[~2011-07-11 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 0:00 feature request: btrfs-image without zeroing data krzf83@gmail.com
2011-07-11 9:31 ` Stephane Chazelas
2011-07-11 12:39 ` krzf83@gmail.com
2011-07-11 12:58 ` Stephane Chazelas [this message]
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=chaz20110711125826.GA18391@seebyte.com \
--to=stephane_chazelas@yahoo.fr \
--cc=krzf83@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).