https://bugzilla.novell.com/show_bug.cgi?id=838475
https://bugzilla.novell.com/show_bug.cgi?id=838475#c18
--- Comment #18 from Gábor Nyers
(In reply to comment #16) [...]
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.
A reasonable compromise.
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.
Well, that doesn't seems to be the case always. This is a brief quote from Jeff from a related mail conversation:
Setting nocow only changes the CoW policy for future overwrites once that file is the sole reference holder of an extent. [...]
This seems to suggest that the NoCoW attribute's current implementation can work in theory, but not very useful for any practical purposes. After all how to make sure that only the a NoCoW'd file(s) will be holding an extent? Care to confirm/deny? -- 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.