#Manjaro up and running... clean. Data all transferred flawlessly.
Now the week long configuration to my needs begins.
My first time with #btrfs
Feels weird using something else than ext4. I hope this wasn't a mistake.
#BtrFS
"some performance improvements and one minor mount option update" are among the main #Btrfs changes merged for #Linux 6.16:
https://git.kernel.org/torvalds/c/5e82ed5ca4b510e0ff53af1e12e94e6aa1fe5a93
A few highlights:
Performance:
- extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime)
- extent io tree cleanups lead to performance improvements by avoiding unnecessary searches or repeated searches
- more efficient extent unpinning when committing transaction (estimated run time improvement 3-5%)
User visible changes:
- remove standalone mount option 'nologreplay', deprecated in 5.9, replacement is 'rescue=nologreplay'
- in scrub, update reporting, add back device stats message after detected errors (accidentally removed during recent refactoring)
Core:
- convert extent buffer radix tree to xarray
- continued preparations for large folios
The btrfs filesystem is now faster on Linux 6.16!
#Linux #Kernel #LinuxKernel #Computers #Laptops #TechNews #TechUpdates #btrfs #filesystem
https://officialaptivi.wordpress.com/2025/05/25/linux-6-16-will-see-more-btrfs-improvements/
Linux 6.16 will see more btrfs improvements
The btrfs filesystem in Linux 6.16 has undergone many improvements that make its performance faster than before. It has already been improved across Linux releases, but the upcoming version of Linux sees even more improvements to this filesystem. Any system that uses this filesystem can now benefit from those improvements.
The buffer conversion work underwent some throughput and runtime improvements for metadata heavy operations, backed by several commits in a pull request made to the 6.16 branch, such as “extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime).”
The tree cleanups have been improved to avoid repeated or unnecessary searches. This improves the I/O performance, should any operation rely on tree cleanups. As for committing transactions, the extent unpinning action has become more efficient than before, yielding a 3-5% performance improvement in runtime.
You can find more about this pull request by clicking on the below button:
Learn more#Btrfs #Filesystem #Linux #LinuxKernel #news #Tech #Technology #update
Desde hace un tiempo, #Btrfs queda bastante mal en las pruebas de rendimiento que hace Phoronix, así que espero que los responsables se pongan las pilas y recorten al menos las diferencias.
Tampoco hace falta ponerse al nivel de XFS, pero es obvio que la situación actual de Btrfs es muy mejorable.
#Linux https://www.phoronix.com/news/Linux-6.16-Btrfs-Performance
@kubuntufocus This may be a stupid questions. #Timeshift supports #BTRFS and other file system. Your focus is on BTRFS. Do I assume correctly that you have chosen to use this approach for better integration and user experience? Will it be available for other OS? Can you start it in case the user interface does not start? Timeshift runs also from the command line. Since you use BTRFS, I guess it can be invoked from a command line too.
Moving Oblivion from btrfs to bcachefs on the same drives drastically improved load times, but broke OBSE - I think due to the case folding?
Does anyone know how to recover a #btrfs raid0, where the disk is fine... It just lost the filesystem signature?
Edit for those tuning in: I got it mounted; I had to copy the superblock on the disk that disappeared; However I still can't automatically mount it as the partition has no readable UUID. Running a scrub now.
Back on #BTRFS after #XFS / #GRUB caused boot failures. First it would work on about every 6th attempt, now it didn't work at all. I'll just mount it with nodatacow, that should give Good Enough TM performance.
Also set up a watchdog a delayed reboot after panic, just to be safe. Should probably also set up a GRUB fallback in case a #NixOS update breaks booting again...
@nen @dalias @tokyo_0 So I was able to run `sudo btrfs check --force --readonly /dev/nvme0n1p3`. And there was an error on checking extents. Tell me if you know what this means.
Okay. So I ran `sudo btrfs scrub start /dev/nvme0n1p3` & `sudo btrfs scrub status /dev/nvme0n1p3` and this is the result.
I still think what was suggested by @tokyo_0 and @dalias - https://mas.to/@tokyo_0/114521284421935167 - is the main reason. Still I'll backup my data as soon as possible.
@tokyo_0 @abhijith @fossunleashed @llutz @zenbrowser (5/5)
It can't be a fluke right if it happened twice.
#ZenBrowser #linux #fedora #fedora42 #gnome #mastodon #fediverse #btrfs
@tokyo_0 @abhijith @fossunleashed @llutz @zenbrowser (4/5)
But, the moment I opened Zen Browser suddenly the filesystem went read-only. Coincidence, I think not. This also happened when I was offline. I opened Zen it showed me the webpage, all good. I reloaded it, it showed me the classic thing "something unexpected happened". All good. But when I closed the #browser, suddenly the FS went read-only.
#ZenBrowser #linux #fedora #fedora42 #gnome #mastodon #fediverse #btrfs
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst