https://bugzilla.novell.com/show_bug.cgi?id=838475
https://bugzilla.novell.com/show_bug.cgi?id=838475#c17
David Sterba
A file with the 'C' attribute set will not be subject to copy-on- write updates. This flag is only supported on file systems which perform copy-on-write. (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.)
Would be interesting to know the reason... incomplete implementation or a more fundamental problem? Anyway, I tried and can confirm.
It's a compromise to keep the implementation sane with the same guarantees. Making any existing file nocow is possible in theory, but the transition would need to be fully crash safe and keeping the intermediate status would need incompatible changes.
Also, a way to shortcut the need to flag files individually with the "C" attribute would be to do this on the directory. All newly created files will inherit it.
This should work for the journal files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.