From: Lubos Kolouch <lubos.kolouch@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Copy/move btrfs volume
Date: Thu, 1 Jul 2010 11:33:59 +0000 (UTC) [thread overview]
Message-ID: <i0huf7$98a$1@dough.gmane.org> (raw)
In-Reply-To: AANLkTin1O6Oa7oq4nFMfNhv4N5FWCko7bcuTMoR5Xkob@mail.gmail.com
Daniel J Blueman, Thu, 01 Jul 2010 12:26:10 +0100:
>> What is the correct way to do this?
>
> The only way to do this preserving duplication is to use hardlinks
> between duplicated files (which reference counts the inode), and use
> 'rsync -H'.
>
> Dan
But when the files are on different snaphots, does rsync see them as
hardlinked?
A scenario - I have raid5 of say, 1TB HDDs. It contains many snapshots.
Then, few years later, new machine is bought and there are, say, 5TB
discs.
So I need to transfer the btrfs volume to the new machine.
But how to do it so that it looks the *same*, ie. the same snapshots?
I could of course write a custom script to create the subvolume, rsync
the files, create snapshot, rsync files, etc,
but it would be nice if the btrfs toolset supports this by default...
Lubos
next prev parent reply other threads:[~2010-07-01 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 10:28 Copy/move btrfs volume Lubos Kolouch
2010-07-01 11:26 ` Daniel J Blueman
2010-07-01 11:33 ` Lubos Kolouch [this message]
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='i0huf7$98a$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).