Transparent compression, snapshots, copy-on-write, deduplication, and data checksumming (and healing via read or scrub) are the main things you might notice as an end-user. BTRFS is mostly on par or slightly slower than other simpler filesystems for speed (can be faster on HDDs due to compression), so if you’re using it you probably want to be taking advantage of the features it offers, not because it’s going to be faster.

As a (semi) power user I also use btrfs subvolumes to create “partitions” (single disk system, @root, @home, @docker), allows for making snapshots only for system or user data, etc.

All around, I love btrfs and I am never going back to journaling fs like ext4

Copy on Write and auto-compression seem like they will free up a bit of space.

That benefit is more theoretical, than practical. The majority of content you have on your drive will be content that is already heavily compressed at the file format level (e.g. images, movies, music) and where additional compression has no effect. So don’t expect any big savings out of the box, you get about 5-15% saving on a regular install.

The real benefit are in the additional functionality it provides, e.g. you can use copy-on-write to make backups of large games before trying to mod them, backups that you might have previously avoided due to 100GB copies taking so long, with BTRFS it is done in a second.

As for BTRFS snapshots you seem to have the wrong idea what they are for. With them you can create backups of your whole filesystem within a second, so you can have full backup in case something goes wrong. With the snapper daemon you can easily automate that make new snapshots every hour and expire them when no longer needed. That’s a really useful thing to have and with BTRFS it’s basically free.

Another big advantage is the ease of partitioning, or the lack of a need for it, with BTRFS subvolumes all your volumes can share the same free space, while still being addressable as separate file systems, e.g. you can have subvolumes for / and /home, without having to guestimate how much space you might need in the future. Can also be abused to install multiple distributions on the same filesystem.

Also checksums, BTRFS will tell you when your data goes bad.

If you don’t think you want snapshotting then dont worry too much about it and use whatever fs you like. if you want a nice btrfs experience try tumbleweed or leap, it is already fully integrated with system and grub , and maintenance with cleanup etc. cobbling together btrfs on your own is fine too but if you miss sometging and mess things up it is usually user error not btrfs error. .

For me, snapshots are the best part of BTRFS because you can easily roll back bad updates without doing a fresh install. It might not be worth reinstalling for, but there’s no reason not to on your next install.

I use BTRFS simply because I run a rolling distro of Linux. For the average user, I don’t think it is quite as necessary but the snapshots are nice. Of course, you could use timeshift to make snapshots as well.

I love btrfs. Mostly, because I had a couple of instances of data loss with ext4, and because it’s far more user friendly than xfs. Btrfs has sane defaults, and when you do want to use the tooling, there’s a lot of good documentation, and it’s mostly straightforward.

That said, unless you have some reason to be mucking around with the fs or want to play with snapshots or such, then I’d say just use your OS defaults.

I’ve installed Timeshift and added the necessary hooks. Now my system gets snapshot’d on every update and the snapshots get added to the GRUB boot menu.

If an update breaks the boot, I can hit the reset button and just boot the old version that still works.

Linux may not have something as powerful as System Restore on Windows, but this comes pretty close.

CoW is pretty bad for performance so you should turn it off in certain cases if you can spare the disk space. The same goes for compression. Both concepts work excellently whens applied to the right files, but they’re not magic.

Timeshift works on other filesystems through hard links and rsync, but the BTRFS support is more powerful.

Yes, snapshots nice to have and compression reduces the disk usage for the operating system and software quite a bit.

For me, BTRFS is worth it for the transparent compression and file integrity checks alone.

I am not sure what Fedora does for virtual machines via boxes (like transparently disabling COW), but one caveat with BTRFS is that you have to be aware that COW is a problem for usage patterns of virtual machines on their images. Just for this one example alone BTRFS is probably not a good fit for the average user.

Another thing which I just learned very recently, is to mount BTRFS volumes with the noatime option significantly speeds up a lot of workloads on my machine (machine has a decent SSD). Again, using the noatime option might create some problems in corner cases, so one should be aware what one is doing.

deleted by creator

It you have a functioning dual boot don’t worry about it. Next install it’s worth looking in into and pretty easy to setup. It has trim support for ssds and is way easier to resize on a live system than lvm with another filesystem

I’m mostly in it for the RAID1 with checksums. If a bit gets flipped, it’ll get flipped right back from the other copy next time the automatic scrub happens. Normal RAID1 can’t do this because, without checksums, it doesn’t know which copy is good.

If you’ve written shell scripts, I don’t think you’re an average user. 😋

I use ZFS, not BTRFS, but both have snapshots, and if you’re someone who likes to tinker with their system like me, it lets you do so without worrying that it will break.

Yes, a few examples of advantages here: https://lemmy.world/post/3197228