Power on hours: 143724
Reallocated sector count: zero
#Btrfs total checksum mismatches: zero
Btrfs total read/write errors: f**king zero
Slow though they may be, hard disk drives are amazing. #SSD s are cool and all, but how often do you find one that's old enough to drive a car and still functioning perfectly?
I migrated to a CoW file system 10 years ago and it never mooed in that entire time.
I'm debating writing a little shell wrapper to list and delete #btrfs snapshots, since they're generally just subvols with predictable names and this kind of thing should be more immediately intuitive than that from CLI.
Edit: I'm going with LUKS + BTRFS. Thanks for the responses!
Which file system should I use for an encrypted root partition on Linux for a single disk (no RAID)?
I typically use LUKS + ext4.
I've also used encrypted BTRFS and ZFS but never worked with them to any extent beyond getting them setup. I see distros such as Fedora are now defaulting to using BTRFS.
I'm seeking some advice: Should I stick with ext4? Or use BTRFS? Or ZFS?
#btrfs-progs 6.13 is out:
https://lore.kernel.org/all/20250214235148.5285-1-dsterba@suse.com/
https://github.com/kdave/btrfs-progs/releases/tag/v6.13
Some highlights:
mkfs:
* new option to enable compression
* updated summary (subvolumes, compression)
scrub:
* start: new option --limit to set the bandwidth limit for the duration of the run
btrfstune:
* add option to remove squota
other:
* a bit more optimized crc32c code
@agu 1,2kg is a pretty steep target, but feasible unless you want a 15" 4k monster with dedicaded GPU.
I'd recommend to use either #LUKS-encrypted #btrfs or #VeraCrypt-encrypted #ext4 for portable storage...
Even more impressively, it actually cleared out some space! I started out with only 16 GB free and now I have 24 GB available for the next procrastination. #Linux #openSUSE #btrfs
sudo btrfs filesystem usage /
[sudo] password for root:
Overall:
Device size: 110.53GiB
Device allocated: 110.53GiB
Device unallocated: 1.00MiB
Device missing: 0.00B
Device slack: 0.00B
Used: 84.10GiB
Free (estimated): 24.80GiB (min: 24.80GiB)
Free (statfs, df): 24.80GiB
Data ratio: 1.00
Metadata ratio: 1.00
Global reserve: 260.77MiB (used: 0.00B)
Multiple profiles: no
Anyone who's good with the #btrfs able to help me here? 
I'm getting "no space left on device" errors from all sorts of things but my disk isn't full. Did I run out of inodes? (is that a thing with btrfs?)
Anything obvious I should try? I'm new to this fs...
A few highlights from the main #btrfs merge for #Linux 6.14:
https://git.kernel.org/torvalds/c/0eb4aaa230d725fa9b1cd758c0f17abca5597af6
- more read IO balancing strategies (experimental config), add two new ways how to select a device for read if […] round-robin, balance reads across devices relevant for the requested IO range
- add encoded write ioctl support to io_uring […]
- support FS_IOC_READ_VERITY_METADATA, applications can use the metadata to do their own verification
I’m in a dilemma - I run #Kubuntu 24.10 on my laptop with all the Plasma 6.1 #Wayland goodness on a #btrfs + LUKS setup and I’ve been meaning to nuke and pave this to a #ZFS + native encryption + #ZFSBootMenu setup. I’m not very keen on using ZFS on a non-LTS release but can’t get Plasma 6.1 on 24.04. I could also use the vanilla #Ubuntu 24.04 with Wayland on ZFS but I’m not keen on #GNOME atm, even though work laptops (to be received soon) will have it (no ZFS or btrfs 
). 
Well fuck me.... This is definitely not the way how I wanted to start my day.
#btrfs #filesystems #sysadmin
Does #btrfs support per-subvolume (or per-folder) profiles yet?
It would be useful to exclude some files (like swap files) from RAID.
