From: Marc MERLIN <marc@merlins.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Planning for subvolumes of subvolumes and btrfs send/receive
Date: Mon, 21 Apr 2014 14:51:21 -0700 [thread overview]
Message-ID: <20140421215121.GR26949@merlins.org> (raw)
In-Reply-To: <747CE4D2-2D83-474D-8D38-E06FF49ACF04@colorremedies.com>
On Mon, Apr 21, 2014 at 12:08:30AM -0600, Chris Murphy wrote:
> I see hard links as completely different to either subvolume/snapshot/reflink. Three hardlinks for a file all point to one file, they're aren't four unique files. But with the latter, three reflinks or snapshots are independent from the parent, including permissions/ACLs, and xattr including selinux labels.
You are correct, but if I'm deduping files for backups of the same data,
hardlinks work fine, but more importantly, they do not get lost if I copy
the filesystem to another machine.
reflink relationship pretty much gets lost no matter what tool you use,
except hopefully btrfs send/receive.
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/
prev parent reply other threads:[~2014-04-21 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 19:46 Planning for subvolumes of subvolumes and btrfs send/receive Marc MERLIN
2014-04-21 5:21 ` Duncan
2014-04-21 5:39 ` Chris Murphy
2014-04-21 5:48 ` Marc MERLIN
2014-04-21 6:08 ` Chris Murphy
2014-04-21 21:51 ` Marc MERLIN [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=20140421215121.GR26949@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).