Bcachefs, Btrfs, EXT4, F2FS & XFS File-System Performance On Linux 6.15
https://www.phoronix.com/review/linux-615-filesystems
Discussions: https://discu.eu/q/https://www.phoronix.com/review/linux-615-filesystems
Quickbeam (a Mac Mini on a shelf in my home office) has been on #btrfs for about three months now. I was vary of it initially, but it is working out nicely so far.
And if it falls apart: no worries, I have backups.
I still worry what will happen if it falls apart, though, because there aren't many other filesystems I'd be happy with. I'm not going to use ZFS while it remains an external module, and then the only other option is LVM + ext4 or xfs (I want snapshots), and LVM+whatever would complicate my backup strategy somewhat.
So here's hoping that btrfs continues to work fine.
@bshah@fosstodon.org If you want something like #btrfs that doesn't suck, there's always #ZFS. Its been actually stable for production use for a decade or two.
#Debian #trixie #kde has been really decent, however here's my biggest hesitation for desktop use (once it goes stable). I'm grateful that #LinuxMint's great #TimeShift app is now Debian-packaged.
I prospectively formatted my root partition as #BTRFS, wanting to make or revert snapshots in Timeshift. But alas, Debian's installer doesn't automagically create BTRFS subvolumes called "@" and "@home", as would be the case in Linux Mint's installer. Without those subvols being created, then Timeshift can't find those subvols, and complains. So no BTRFS snapshotting/restoring can be done in Timeshift. 
So! A weekly drive of yee old #Fedora :) That is, first I did workstation, then I did #FedoraAtomic with #Cosmic - because I can.
#Btrfs home subvolume allows this by making it so I don't have to reinstall a damn thing :)
In any case, it's great! GNOME 48 is pretty sleek, though on my machine COSMIC ran better - albeit on a 2013 2 core i5... but yeah, GNOME "felt" more responsive :3
Now I return to #NixOS because I kind of feel naked without it 
Oh beautiful #COSMIC, how weird it was to try your 7th alpha, by nuking and paving the #Fedora Workstation #distribution, only to replace it with Fedora Atomic Cosmic.
Again, I'm using #BTRFS with subvolumes. The "@" subvolume being recreated for probably the 7th time, effectively just deleting the old volume and making a new one - sort of releasing all the storage space of the original.
The "@home" subvolume has been there for a while - even retaining the COSMIC settings from #NixOS.
Ich nutze seit langer Zeit #Manjaro, weil ich unbedingt eine #Wayland Session wollte und das aktuellste KDE Plasma.
Das Manjaro betreibe ich im Testing stage ohne ein Problem. Die Installation ist auf einem #Btrfs Filesystem und falls mal was schief geht kann ich im Grub den letzten Stand zurück rollen.
Ob das jetzt für jeden optimal ist, kann ich nicht beurteilen. Für mich ist es perfekt.
What's the correct way to restore BTRFS snapshot on non-root subvolume? #partitioning #backup #btrfs
Updating initramfs breaks the kernel on fd luks encrypted Ubuntu 24.04 #kernel #luks #initramfs #btrfs
I have just nuked the #btrfs subvolume for the root of #NixOS and paving it with #Fedora 42. My home subvolume untouched is now part of the new system and voila:
EVERYTHING WORKS.
Besides GNOME extensions and wallpapers, which is to be expected, the browsers, the menu, the GNOME settings in general just works.
I've completely switched the base of my #Linux distribution - and it's almost like nothing happened at all.
@9Lukas5 how about letting the system do that? What I'd love to see is a standardization of using #btrfs snapshots as a form of system images.
#Manjaro is using #ArkaneLinux as inspiration by using their #arkdep tool to deploy arch systems to btrfs snapshots.
It would be cool to see the transition between all 3, going from #NixOS, to Arkane, to #Fedora, and back.
Still waiting for #GNOME 48 to hit #nixpkgs - but was also thinking of making a temporary switch - to #Fedora 42.
Riddle me this, my little scatlings: with the SSD divided up into #BTRFS subvolumes, what's to prevent me from just deleting and recreating the root subvolume (which for historical purposes is dubbed "@") to then install Fedora 42 to try the latest edition?
Again, the #nix flake remains in the "@home" subvolume, meaning I could always bring back #NixOS to its previous state.
Hey @fedora, I was reading the article series about #btrfs but it seems that the articles about qgroups and RAID were never written? Or am I missing something?
https://fedoramagazine.org/working-with-btrfs-general-concepts/
point of order this is on dedicated battery backup and can run uninterrupted with all accoutrement for about 2 hours, i think it's only lost power once. that rack has lost it entirely only twice. the first time was how i found out that apparently Cyberpower has had some SKUs that over the years betray you in the '10s. the networking and hypervisor were on the bottom rack UPS-backed power. networked UPS status is possible, too.
