From: Lubos Kolouch <lubos.kolouch@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Copy/move btrfs volume
Date: Thu, 1 Jul 2010 10:28:36 +0000 (UTC) [thread overview]
Message-ID: <i0hqkk$r4h$1@dough.gmane.org> (raw)
Hello,
I am testing btrfs on one of our backup servers
(many millions of files, 1.5TB size, running on (non-btrfs-provided-)
raid5).
I am using subvolumes/snapshots with following rsync.
It works very well, but I would like to ask a question... say I would need
to copy/move the files to different server/disk.
Normally I would do it with rsync, but I guess it will not preserve the
subvolumes, it will also not detect that they are the same files (I guess
they are not just normal hardlinks). So I would end up with duplicated
files.
What is the correct way to do this?
Thank you and best regards
Lubos Kolouch
next reply other threads:[~2010-07-01 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 10:28 Lubos Kolouch [this message]
2010-07-01 11:26 ` Copy/move btrfs volume Daniel J Blueman
2010-07-01 11:33 ` Lubos Kolouch
2010-07-01 22:21 ` Matt Brown
2010-07-02 6:15 ` Oystein Viggen
2010-07-03 7:33 ` Lubos Kolouch
2010-07-21 15:00 ` Hubert Kario
2010-07-02 1:29 ` Chris Mason
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='i0hqkk$r4h$1@dough.gmane.org' \
--to=lubos.kolouch@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).