From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Can you keep reflink relationship during a copy/backup to another filesystem?
Date: Tue, 28 Jan 2014 23:50:25 -0800 [thread overview]
Message-ID: <20140129075025.GM14998@merlins.org> (raw)
So I used to use hardlinks to do historical backups of the same filesystem
but I know it's preferable to use refllink with btrfs to avoid having too
many hardlinks.
But if I need to backup this filesystem to another one some other way than
btrfs send/receive (let's say cp -a, tar, or rsync), is it correct to say
that reflink relationships will be lost and my data will take more space?
That is unless the target filesytem can do deduplication like btrs now can?
(I haven't tried it yet, but it's about time that I do)
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next reply other threads:[~2014-01-29 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 7:50 Marc MERLIN [this message]
2014-01-29 8:05 ` Can you keep reflink relationship during a copy/backup to another filesystem? Hugo Mills
2014-02-07 23:05 ` Marc MERLIN
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=20140129075025.GM14998@merlins.org \
--to=marc@merlins.org \
--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).