this post was submitted on 30 Jan 2024
27 points (93.5% liked)

Linux

8066 readers
66 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
[email protected]
27
tell me your experience using zfs/btrfs (programming.dev)
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
9 comments fedilink hide all child comments
 

Hey,

I am planning to implement authenticated boot inspired from Pid Eins' blog. I'll be using pam mount for /home/user. I need to check integrity of all partitions.

I have been using luks+ext4 till now. I am ~~hesistant~~ hesitant to switch to zfs/btrfs, afraid I might fuck up. A while back I accidently purged '/' trying out timeshift which was my fault.

Should I use zfs/btrfs for /home/user? As for root, I'm considering luks+(zfs/btrfs) to be restorable to blank state.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 9 months ago

I have been using btrfs for years, and love it. I chose it over zfs mainly because I found the tooling easier and more straightforward, and concepts less complex. It's been a long time, but I also believe btrfs was in mainline and zfs wasn't, and having reliable access to rescue tools was important - any complexity like having to build my own rescue disks was highly undesireable. I also vaguely remember zfs needing regular maintenance back in the day, which would have influenced my decision. I've also liked that btrfs tools have smart defaults, such as detecting SSDs and auto-setting healthy defaults. I'm not a sysadmin, and have no interest in being one, so I value features like these.

Anyway, I've had ext3 and ext4 corruption issues several times over the years, but have had no issues with any btrfs filesystems. I've used it on platters, SSDs, SD cards, USB sticks -- except for vfat and iso9660 for specialty devices, I can't say I've chosen anything other than btrfs for over a decade, and I've a few ext4 partitions to btrfs in fury after corruptions, repairs, and restores.

I'm sorry I can't compare btrfs to zfs; zfs has probably fixed the tooling warts and licensing issues that I remember from years ago, by now. Lots of people like it, so both are good choices.