<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Tue, Jan 17, 2023, at 11:40, Hubert Chathi wrote:<br></div><blockquote type="cite" id="qt" style=""><div>On Mon, 16 Jan 2023 17:45:25 -0500, Chris Irwin via kwlug-disc <<a href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a>> said:<br></div><div><br></div><div>[...]<br></div><div><br></div><div>> People claim ZFS handles databases/VMs better than btrfs, but I don't<br></div><div>> really see how since it appears to use the same COW semantics. Perhaps<br></div><div>> it's just hidden behind better caching.<br></div><div><br></div><div>FWIW, you can disable COW on btrfs for certain files, if you want better<br></div><div>performance for databases/VM images by using the +C file attribute .<br></div></blockquote><div><br></div><div>True, but if you're disabling COW, you're probably using the wrong filesystem.<br></div><div><br></div><div>* You will lose any and all data integrity on those files, as checksumming won't occur.<br></div><div><br></div><div>* Snapshots rely on COW, so if you snapshot a file with COW disabled, writes will be COW anyway.<br></div><div><br></div><div>If you're not using snapshots, and don't have any data integrity, there's really no reason to use btrfs.<br></div><div><br></div><div id="sig91988184"><div class="signature">-- <br></div><div class="signature"><b>Chris Irwin</b><br></div><div class="signature"><br></div><div class="signature"><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">email: chris@chrisirwin.ca</span><br></div><div class="signature"><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"> web: <a href="https://chrisirwin.ca">https://chrisirwin.ca</a></span><br></div></div><div><br></div></body></html>