I want to eliminate the COW feature on all of my OS files. It is a nice
feature for user files, but I don't see a clear benefit for the actual
OS files. And I suspect that COW induced fragmentation is causing or
aggravating problems with my system including the boot open_ctree
problem. I had planned to recursively chattr these files to "nodatacow"
status but then I ran into this cryptic warning on the chattr man page:
(Note: For btrfs, the 'C' flag should be set on new or empty files. If
it is set on a file which already has data blocks, it is undefined when
the blocks assigned to the file will be fully stable. If the 'C'
flag is set on a directory, it will have no effect on the directory,
but new files created in that directory will the No_COW attribute.)
So what exactly does that mean? Does it mean that it is unsafe? Or
does it mean that it is simply unreliable? If I run a btrfs balance
first will that clear out the COW snapshots and enable me to perform the
recursive chattrs? What is the best way to approach this?
Thanks for any tips, George
--
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
