Difference between revisions of "Talk:Btrfs"
(→cp --reflink and the actual meaning of CoW: new section)
m (→cp --reflink and the actual meaning of CoW: unsigned)
|Line 20:||Line 20:|
Revision as of 12:55, 27 May 2017
"Displaying used/free space" needs rewrite
Section "Displaying used/free space" needs a rewrite. I will hopefully do that when I have time.
- The example with /usr/bin/df is misleading (on simple setups it's reporting disk usage ('used' value) quite accurate).
- "btrfs filesystem usage" should be mentioned on top
- there should be a link to https://btrfs.wiki.kernel.org/index.php/FAQ#How_much_free_space_do_I_have.3F
Proposal to add lzo compression warning
The Debian btrfs page has a warning about compress=lzo being possibly dangerous, citing the thread here. I propose adding a warning section that simply notes this possibility and cites either the Debian wiki, the linked thread, or both. -- altercation
- It might be worth a note pointing to the thread, but the user in that thread reports he was using RAID6, which is already warned against in the wiki article. The rest of it seems to be just guessing that lzo is affecting it. Hard to know since he was using RAID6. -- Rdeckard (talk) 00:50, 23 March 2017 (UTC)
If one wishes to create a lightweight copy, --reflink must be used even on files with CoW enabled. Anyone on btrfs filesystem can easily test this. Claims of this being required for only files with CoW explicitly disabled are false. --reflink is not the same thing as CoW - this is better explained in https://btrfs.wiki.kernel.org/index.php/SysadminGuide#Copy_on_Write_.28CoW.29