On 2015-01-08 19:24, Konstantinos Skarlatos wrote: >> Anyway, given the pros and cons I have now changed journald to set >> the nocow bit on newly created journal files. When files are >> rotated (and we hence know we will never ever write again to them) >> the bit is tried to be unset again, and a defrag ioctl will be >> invoked right after. btrfs currently silently ignores that we unset >> the bit, and leaves it set, but I figure i should try to unset it >> anyway, in case it learns that one day. After all, after rotating >> the files there's no reason to treat the files special anymore...
> Can this behaviour be optional? I dont mind some fragmentation if i > can keep having checksums and the ability for raid 1 to repair those > files. I agree with Konstantinos's request: please let this behavior optional. BR G.Baroncelli -- gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
