On 17 October 2016 at 13:08, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
b) btrfs is not particularly friendly to some workloads like database or VM image. Again, storing such data in separate subvolume provides for disabling offending btrfs features (CoW in the first place) per-subvolume.
MINOR CORRECTION (ie. I actually agree with most of what you said and the thrust of your argument) You can actually disable CoW on a folder or files within a subvolume - NoCoW is not an attribute of a Subvolume, but an xattr applied to files. If applied to a directory, the attribute is automatically set on all files created in that directory from that point on. In openSUSE, the YaST installer will set NoCoW on certain mountpoints of certain subvolumes, so the effect is exactly as you described above But I just wanted to clear up it's not a Subvolume feature, you can turn CoW off wherever you want :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org