Re: Moving contents from one subvol to another

2014-11-30 Thread Shriramana Sharma
On Sun, Nov 30, 2014 at 9:23 AM, Shriramana Sharma samj...@gmail.com wrote: Why should noCoW affect cp --reflink anyhow? I just created a 500 MiB file from /dev/urandom under a chattr +C-ed dir, and copied to another subvol using cp --reflink, and fi df still shows 500 MiB, not 1 GiB. Looks

Moving contents from one subvol to another

2014-11-29 Thread Shriramana Sharma
Hello. I am now taking the first steps to making my backup external HDD in BtrFS. From http://askubuntu.com/questions/119014/btrfs-subvolumes-vs-folders I understand that the only difference between subvolumes and ordinary folders is that the former can be snapshotted and independently mounted.

Re: Moving contents from one subvol to another

2014-11-29 Thread Hugo Mills
On Sat, Nov 29, 2014 at 07:51:07PM +0530, Shriramana Sharma wrote: Hello. I am now taking the first steps to making my backup external HDD in BtrFS. From http://askubuntu.com/questions/119014/btrfs-subvolumes-vs-folders I understand that the only difference between subvolumes and ordinary

Re: Moving contents from one subvol to another

2014-11-29 Thread Shriramana Sharma
On Sat, Nov 29, 2014 at 7:58 PM, Hugo Mills h...@carfax.org.uk wrote: The latest version of mv should be able to use CoW copies to make it more efficient. It has a --reflink option, the same as cp. Note that you can't make reflinks crossing a mount boundary, but you can do so crossing a

Re: Moving contents from one subvol to another

2014-11-29 Thread Robert White
On 11/29/2014 07:15 AM, Shriramana Sharma wrote: On Sat, Nov 29, 2014 at 7:58 PM, Hugo Mills h...@carfax.org.uk wrote: The latest version of mv should be able to use CoW copies to make it more efficient. It has a --reflink option, the same as cp. Note that you can't make reflinks crossing a

Re: Moving contents from one subvol to another

2014-11-29 Thread Shriramana Sharma
On Sat, Nov 29, 2014 at 10:37 PM, Robert White rwh...@pobox.com wrote: One thing to keep in mind is that mv, when crossing any of these boundaries degenerates to a copy-and-remove operation and _none_ of the source files will be removed until _all_ of the files have been copied. If any of the