- cross-posted to:
- linux@zerobytes.monster
- cross-posted to:
- linux@zerobytes.monster
Ted Ts’o sent out the EXT4 updates today for Linux 6.11. He explained in that pull request:
“Many cleanups and bug fixes in ext4, especially for the fast commit feature. Also some performance improvements; in particular, improving IOPS and throughput on fast devices running Async Direct I/O by up to 20% by optimizing jbd2_transaction_committed().”
My experience is based on running that btrfs array since 2019. It’s still running in production on my server, I still use it daily, and the data I keep on it is still accessed, processed, indexed, and backed up every day. It’s not an experiment for the sake of a blog post, it’s a thing that is part of my personal infrastructure. The reason I update that post periodically is because I learn something new, or something minor has changed and the text should be updated to reflect that. If using btrfs on a busy server every day is the experience of 2019, I don’t know what to say to that.
Oh that’s hugely different then. It was not apparent that you were using this setup since the initial blog post. Maybe make a note at the top of the post, so your message (like here) is understood. Don’t get me wrong, I appreciate the clear information you give here and your feedback on how this works. From your report and given its the default FS for Fedora, its absolutely clear that I need to review my bias and view as BTRFS as a contender for my next system drive.
I had intended that the dates on the edits would have suggested otherwise (the last was 20230422), but I also get how easy it is to miss them if you’re looking for something specific. I can’t change the publication datestamp because that’s part of the slug, and it would break links both internal and any that are external.