Another weird thing I've noticed. I did this: chattr +C /mnt/btrfs/vms
But both of these report nothing: lsattr /mnt/btrfs/vms lsattr /mnt/vms Shouldn't at least one show the C attribute? On Tue, Aug 18, 2015 at 1:36 PM, Timothy Normand Miller <theo...@gmail.com> wrote: > Maybe this is a dumb question, but there are always corner cases. > > I have a subvolume where I want to disable CoW for VM disks. Maybe > that's a dumb idea, but that's a recommendation I've seen here and > there. Now, in the docs I've seen, +C applies to a directory. Does > it apply to subvolumes? And do I apply it to the subvolume within the > main volume, or do I apply it to the mount point where I've mounted > the subvolume separately? Are there any cases where the flag applies > or not depending on how you access the files? > > The same subvolume for me is accessible via /mnt/btrfs/vms (via the > /mnt/btrfs mount point) and /mnt/vms (where the subvolume is mounted). > I applied +C to /mnt/btrfs/vms. So what I'm trying to find out is if > it also applies when files are accessed via /mnt/vms. > > Thanks. > > > -- > Timothy Normand Miller, PhD > Assistant Professor of Computer Science, Binghamton University > http://www.cs.binghamton.edu/~millerti/ > Open Graphics Project -- Timothy Normand Miller, PhD Assistant Professor of Computer Science, Binghamton University http://www.cs.binghamton.edu/~millerti/ Open Graphics Project -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
