> "Butter FS" est l'un des systèmes de fichiers les plus avancés disponibles aujourd'hui sous Linux. Il est moderne, repose sur des principes qui le rendent extrêmement fiable et propose de nombreuses fonctionnalités très intéressantes.

> Malgré cela, il se traîne une mauvaise réputation qui freine son adoption. Mais cette réputation est-elle vraiment justifiée ?

**Btrfs : révolution ou catastrophe ? Où en est-on aujourd'hui ?** par @FLOZz (2022)

https://blog.flozz.fr/2022/05/22/btrfs-revolution-ou-catastrophe-ou-en-est-on-aujourdhui/

I guess it's time to finally decide (currently leaning towards 1)...

#nas #btrfs #zfs

Mes y medio usando #OpenSuse y gratamente sorprendido por la maravilla que es el sistema de archivos #Btrfs, con sus subvolúmenes y snapshots, que me ha permito hacer un backup automatizado incremental rápido y eficiente. Al principio desconcertante, pero no tan difícil de entender con un buen tutorial

https://www.youtube.com/watch?v=_z1VoXmIBBs

dear lord another one, everybody read up to avoid losing data

https://blog.fyralabs.com/btrfs-corruption-issues/

#tech #linux #btrfs #advisory #fedora #ultramarinelinux

Des personnes par ici ont de l'expérience avec l'utilisation combinée de #bcache et #btrfs ?
Vous auriez des retours d'expérience et conseils / recommandations ?

C'est pertinent comme cache en lecture (surtout) si on a une asymétrie du style 500Go de SSD pour >10To de HDD ?
Il me semble que pour mon cas d'usage c'est la lecture aléatoire qui est la plus pénalisante.

1/3

Ich lese btrfs immer als Butterfass.

BTRFS Subvolumes On Debian Trixie - Easiest Tutorial

https://video.fosshq.org/w/oAvTi9AjjREdJRzEM7dqdZ

I have a bunch of old documents on my computer separated in an "old documents" folder. Currently they are not compressed.
If I compress my "old documents" into a tar.zst archive, will I increase to decrease the probability of them becoming corrupted?

My home partition is using BTRFS if it matters. #BTRFS

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:

Cover image credit.

Does anyone know how to recover a #btrfs raid0, where the disk is fine... It just lost the filesystem signature?

Hear me out.

So, I'm facing a weird issue with my #fedora workstation. The filesystem goes "read-only" at random times and I dont know why. I've do a reboot to fix it. Do you have any idea about this and how to fix it ?