Massimo-B

Today going to start v0.10-57-ge403398-dirty on my problematic 1TB HDD. First tests on SSDs have been successful. Before I would like to optimize the free space fragmentation: > btrfs-balance-least-used with...

> You can also use `btrfs balance start -dusage=80 /mnt/btrfs` > > Never use `-musage` or balance metadata when not converting to a different profile. It will delete existing metadata...

> It makes metadata more compact, and thus more likely it want to allocate a new block group metadata---if it's not possible, you may be stuck since deleting things requires...

> automatically as needed with `echo 75 | tee /sys/fs/btrfs/*/allocation/data/bg_reclaim_threshold`. Interesting, I learned more about balancing and this auto-balancing from https://wiki.tnonline.net/w/Btrfs/Balance > The bad case is when metadata grows to...

> @Massimo-B I still think all of this is a concern for you because you use btrfs as a backup vault, and try using bees to keep the vault as...

> @Massimo-B I still think all of this is a concern for you because you use btrfs as a backup vault, and try using bees to keep the vault as...

> `btrfs-balance-least-used -u 80` > You can also use > `btrfs balance start -dusage=80 /mnt/btrfs` > The knorrie version does a better job than plain `btrfs balance` because it frees...

> The knorrie version does a better job than plain `btrfs balance` because it frees least used chunks first, possibly filling other considered chunks to the max so it can...

It seems I damaged that btrfs now: https://github.com/knorrie/python-btrfs/issues/51#issuecomment-2615837284

All the recommendations are targetting the free space fragmentation and therefore the write performance. **But how to improve the read performance?** After another damaged btrfs (https://lore.kernel.org/linux-btrfs/[email protected]/), this time it damaged...