A bunch more manual xfs repairs over the past week. In contrast, there's been exactly zero ext4 or btrfs manual fsck's needed for the same environments. All with some flavor of EL8 or EL9 on two different storage platforms (Ceph, Longhorn). Still no idea what's causing it, but xfs continues to be the outlier.
#btrfs
2 posts2 participants0 posts today
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
www.phoronix.comBcachefs, Btrfs, EXT4, F2FS & XFS File-System Performance On Linux 6.15With the copy-on-write Bcachefs file-system considering its on-disk format now 'soft frozen' and nearing the point of potentially removing the 'EXPERIMENTAL' flag on it, a number of Phoronix readers have been requesting some fresh benchmarks of this open-source file-system.
#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. 
Replied in thread
What's the correct way to restore BTRFS snapshot on non-root subvolume? #partitioning #backup #btrfs
Ask UbuntuWhat's the correct way to restore BTRFS snapshot on non-root subvolume?I want to be able to restore BTRFS snapshots on non-root subvolume such as external hard drive for example.
# snapper -c myconfig rollback 1
Command 'rollback' cannot be used on a non-root subvolume /
Updating initramfs breaks the kernel on fd luks encrypted Ubuntu 24.04 #kernel #luks #initramfs #btrfs
Ask UbuntuUpdating initramfs breaks the kernel on fd luks encrypted Ubuntu 24.04I have Installed Ubuntu 24.04 on btrfs on a Luks encrypted harddrive with /boot/efi on a separate partition. It was running fine until I messed up trying to unlock using fido2luks
and since that di...
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/
Fedora Magazine · Working with Btrfs – General Concepts - Fedora MagazineThis article is part of a series of articles that takes a closer look at Btrfs, the default filesystem for Fedora variants since Fedora 33.
Continued thread
So, I’ve basically reinstalled the system from a USB drive and am now restoring #backups. Luckily, I backed up all the #Dotfiles and configurations and so the #desktop is behaving as before, which is a big relief. On the up side, it’s booting a lot faster and the #disk has #btrfs #partition, rather than #Ext4.
Blogged: Resizing a LUKS-backed BTRFS RAID1 filesystem
https://www.kassner.com.br/en/2025/04/12/luks-btrfs-raid1-resize/
Rafael Kassner · Resizing a LUKS-backed BTRFS RAID1 filesystemHi.
After a series of hardware upgrades, I finally have 2x 2TB SDD for data on my NAS! However, they are still configured with ~900GiB data partitions, and today it is time to expand it!
Initial state The current disk layout is:
# fdisk -l /dev/sda Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: PNY CS900 2TB SS Sector size (logical/physical): 512 bytes / 512 bytes Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 499711 497664 243M 83 Linux /dev/sda2 499712 43468799 42969088 20.5G 83 Linux /dev/sda3 43468800 1918322687 1874853888 894G 83 Linux # fdisk -l /dev/sdb Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: Samsung SSD 870 Sector size (logical/physical): 512 bytes / 512 bytes Device Start End Sectors Size Type /dev/sdb1 2048 1001471 999424 488M Linux filesystem /dev/sdb2 1001472 98656255 97654784 46.6G Linux filesystem /dev/sdb3 98656256 1973510143 1874853888 894G Linux filesystem Reading the output above, the data partitions can be found at /dev/sd*3, both sized at 894GiB with the exact same sector size (512 bytes) and sector count (1874853888).
My experience with #FlashDrives recently has been mixed. I have no problem in encrypting them with #LUKS, using #cryptsetup or with formatting a partition with #Btrfs, for instance, using #gparted and doing other tinkering with #Gnome #disks. But the problem has been with the actual drives themselves. The cheaper ones seem to have quite a few bad sectors, etc. and so they’re not really reliable for medium term storage.
1/2
Anfang des Jahres hat @ammoniumperchlorate einen Vortrag darüber gehalten, wie wir unsere Mastodon-Instanz rheinneckar.social dank #btrfs und #NixOS mit nur wenigen Sekunden Downtime auf einen neuen Server umgezogen haben. Definitiv sehenswert! 
finally i setuped my laptop with #btrfs + #impermanence + #nixos !
the /persist snapshot is transferred to my mini pc's hdds via btrbk.
Eigentlich wollte ich den #Linux Kernel 6.14 testen, aber #initramfs, #btrfs und #nvidia sagen nein.
Here’s a thought I’ve just had on file systems for #Linux: if I have no need for advanced features like subvolumes or snapshots or built-in support for multiple devices, is there really a point to thinking about which file systems is good for an Average Jane such as myself? I don’t exactly consider myself lacking in bandwidth, so surely the difference only starts to matter at scale? #btrfs #ext4 #xfs
hey hey #Linux #FileSystem #ZFS #RAID #XFS entities! I'm looking for extremely opinionated discourses on alternatives to ZFS on Linux for slapping together a #JBOD ("Just a Bunch Of Disks", "Just a Buncha Old Disks", "Jesus! Buncha Old Disks!", etc) array.
I like ZFS but the fact that it's not in tree in-kernel is an issue for me. What I need most is reliability and stability (specifically regarding parity) here; integrity is the need. Read/write don't have to be blazingly fast (not that I'm mad about it).
I also have one #proxmox ZFS array where a raw disk image is stored for a #Qemu #VirtualMachine; in the VM, it's formatted to XFS. That "seems" fine in limited testing thus far (and quite fast, so it does seem like the defaults got the striping correct) but I kind of hate how I have multiple levels of abstraction here.
I don't think there's been any change on the #BTRFS front re: raid-like array stability (I like and use BTRFS for single disk filesystems but) although I would love for that to be different.
I'm open to #LVM, etc, or whatever might help me stay in tree and up to date. Thank you! Boosts appreciated and welcome.
#techPosting
Continued thread
I just installed Arch manually, but now it fails to boot. It only asks to unlock nvme1n1p1, but not the root, leading to a "failed to find root" error.
fstab seems correct. I suspect the issue is in crypttab.
Does anyone know a good blog post or guide to set it up correctly? I feel like I’m close to solving this.
#ArchLinux #Btrfs #LVM #LUKS #Linux
1/2