On Fri, Apr 28, 2017 at 11:41:00AM -0600, Chris Murphy wrote: > The same behavior happens with NTFS in qcow2 files. They quickly end > up with 100,000+ extents unless set nocow. It's like the worst case > scenario.
You should never use qcow2 on btrfs, especially if snapshots are involved. They both do roughly the same thing, and layering fragmentation upon fragmentation ɪꜱ ɴᴏᴛ ᴘʀᴇᴛᴛʏ. Layering syncs is bad, too. Instead, you can use raw files (preferably sparse unless there's both nocow and no snapshots). Btrfs does natively everything you'd gain from qcow2, and does it better: you can delete the master of a cloned image, deduplicate them, deduplicate two unrelated images; you can turn on compression, etc. Once you pay the btrfs performance penalty, you may as well actually use its features, which make qcow2 redundant and harmful. Meow! -- Don't be racist. White, amber or black, all beers should be judged based solely on their merits. Heck, even if occasionally a cider applies for a beer's job, why not? On the other hand, corpo lager is not a race. -- 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
