@pete I made the mistake of using btrfs once. Never again.
@lukedashjr I've used it on most of my machines for years, both with and without RAID1. Never had any issues. And it's checksums have saved me from failing hardware on a few occasions.
@pete btrfs got to the point my IRC connections were timing out because the IRC client was blocking on writing log files...
@lukedashjr How long ago was that?
Many years ago there were performance issues like that. But they seem to have been fixed.
@pete Maybe a year ago.
@pete I also didn't like the fact that when I found a bug, I had to fix it myself. :p
@lukedashjr What hardware setup? Any unusual usage patterns? Use of snapshots heavily?
All the performance sensitive stuff I use it for is on ssd's; I use it on backup drives too. But if they had latency spikes I'd never notice.
@pete Daily snapshots for years.
@lukedashjr That might be it then. I don't keep more than a few dozen snapshots.
The slowest thing I do on a regular basis with btrfs is send/recv snapshots of my Monero node. Monero seems to make it's block database very fragmented due to heavy use of sparseness.
@JuergenStrobel @lukedashjr I do use sparse files with btrfs regularly because I use it for Qubes: the VM's disk images are stored as sparse files. But my overall usage patterns are probably relatively benign as other than write once media all my data easily fits into cache (my desktop has 64GiB, and my laptop, 32GiB).
That actually helps with fragmentation these days due to delayed allocation: where data is written to disk is chosen just prior to flushing.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!