Re: [PATCH 0/2] btrfs: allow cross-subvolume BTRFS_IOC_CLONE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I am very happy to see this patch. It was one of the first thing I
tried after making a subvolume, cp --reflink, and it failed. I'll have
to try this out.

Jérôme Poulin

On 2011-04-02, at 12:56, Larry D'Anna <larry@xxxxxxxxxxxxxx> wrote:

> * Ken Drummond (btrfs@xxxxxxxxxxxxxxx) [110402 11:51]:
>> I don't really understand the details here, but doesn't the creation of
>> a snapshot already lead to data extents being shared between
>> sub-volumes?  From a simple user perspective this sounds like a very
>> useful capability.
>
> I was surprised and frustrated to find it missing.  I had just copied a large
> quantity of data into btrfs, realized i need to make a subvolume to try out
> snapshotting, and then found out i had to copy all the data *again* to get it
> into a subvolume.  There are tons of scenarios where users will want and expect
> to be able to do this.
> --
> 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
--
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


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux