You are not logged in.
Hello people. By saying non-cloned, I mean any file that has the CoW attribute but doesn't use it. Writing over it (non-truncating) makes allocations outside boundaries of original file. Original file is being protected like if it is cloned. That doesn't make sense.
Can somebody explain that?
Offline
Maybe because btrfs does not really enabled CoW on it? CoW can be enabled on empty files only. If you had a non-empty file and then set +C attribute then btrfs still be going to use CoW for this file.
Read it before posting http://www.catb.org/esr/faqs/smart-questions.html
Ruby gems repository done right https://bbs.archlinux.org/viewtopic.php?id=182729
Fast initramfs generator with security in mind https://wiki.archlinux.org/index.php/Booster
Offline