On Apr 20, 2014, at 11:48 PM, Marc MERLIN <marc@xxxxxxxxxxx> wrote: > On Sun, Apr 20, 2014 at 11:39:22PM -0600, Chris Murphy wrote: >> >> On Apr 20, 2014, at 1:46 PM, Marc MERLIN <marc@xxxxxxxxxxx> wrote: >> >>> Can you help me design this right? >>> >>> Long story short, I'm wondering if I can use btrfs send to copy sub >>> subvolumes (by snapshotting a parent subvolume, and hopefully getting >>> all the children underneath). My reading so far, says no. >> >> That's my understanding thus far also. Seems like first a recursive read-only snapshot creation is a pre-requisite, since a read-only snapshot is needed first in order to send it. >> >> I think the seed device method is a better way to do this, though I'm not sure what state its in. > > Thank you both for the confirmation. > > This indeed makes it too much of a pain for me, so I think I will go > back to making hardlinks like I did with ext4 > That way I won't need subvolumes of subvolumes and will be able to do > snapshots and replication more easily. 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. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
