News for hackers. Stuff that matters.
Re:ZFS, BTRFS, XFS, EXT4 and LVM with KVM – A Storage Perfor... by ryao on Sunday May 22, 2016 @04:02PM (#11750026)
Are you sure that disabling CoW solves btrfs' fragmentation issue when you pre-allocate the image? If the volume is snapshotted regularly, CoW should be active once on each extent once until the next snapshot reactivates it. That should mean that the fragmentation would still occur, although more slowly. Is that correct or am I misunderstanding something?

I am only superficially familiar with btrfs internals, but I do not see any way to implement snapshots without either doing CoW or duplicating the data in its entirety. If you are checking to see if the data is part of a snapshot, then you should be doing CoW.

Re:ZFS, BTRFS, XFS, EXT4 and LVM with KVM – A Storage Perfor... by josefbacik on Monday May 23, 2016 @02:20AM (#11752237)
Yeah nocow only works if there are no snapshots, which is why we have to check, so if you use snapshots it falls back to COW.
Re:ZFS, BTRFS, XFS, EXT4 and LVM with KVM – A Storage Perfor... by MertsA on Sunday May 22, 2016 @06:42PM (#11750604)
Disabling CoW disables snapshotting.
Re:ZFS, BTRFS, XFS, EXT4 and LVM with KVM – A Storage Perfor... by versteegen on Sunday May 22, 2016 @10:37PM (#11751452)
(I'm not an expert, just a user) Snapshotting effectively disables NOCOW. Snapshotting always works, and needs COW to do so. Which means ryao is right that fragmentation will occur. btrfs doesn't copy a NOCOW file in its entirety if it's in a snapshot, or I would have run out of disk space by now. (I really need to move my VM images to a non-backed-up subvolume.)
Re:ZFS, BTRFS, XFS, EXT4 and LVM with KVM – A Storage Perfor... by josefbacik on Monday May 23, 2016 @02:17AM (#11752230)
No it doesn't.