Hacker News new | past | comments | ask | show | jobs | submit login

> I'd advise you to use PPA over repo though, as many key features are missing from the version on repos.

I would advise using ZFS only with distros that come with it (i.e. Ubuntu, Proxmox), especially if you plan to have your / on it. I wasted too much time on CentOS with ZFS, would not do it again.




ZFS on Root just sounds like pain to me. I opt for MD RAID on root and then ZFS my other volumes.

I would also say Ubuntu is probably the better choice for Linux ZFS, as CentOS seems to be lacking good support.


Once you try it, you're never going back. Snapshots are made for things like system administration. Upgrade borked your system? Just rollback.

Want to use the last version of your firewall config? I wrote a utility you might like to try, httm[1], which allows you to restore from your snapshot-ed unique versions.

If you like ZFS, then trust me you have to have ZFS on root.

[1]: https://crates.io/crates/httm


Had you previously done a Show HN on this? I feel like I saw it once before.


Someone else posted about it awhile ago: https://news.ycombinator.com/item?id=31184404


ZFS on root is really amazing on FreeBSD and the advantage is that you can snapshot your boot drive.


have a look at Boot Environments. It really is amazing.


Yes I know, bectl. I use it.

I just didn't want to mention it because the discussion was mainly about Linux. But FreeBSD has a really strong toolchain for this indeed.


Also a Solaris thing, yeah? (beadm etc)


Yeah, Ubuntu has done a pretty good job with ZFS on root installation.

Zero setup, works out of box. Highly recommend ZFS and Ubuntu with ZFS!


I think for me I am more concerned about trying to get the OS bootable again, if something becomes corrupted on the OS level. Even with MD RAID it came be a bit of a struggle to recover, but ZFS on Root seemed much harder to troubleshoot and repair. Perhaps I am mistaken in this belief though?


In Ubuntu’s implementation, root and boot are separate pools (bpool, rpool). Both are (and can be manually) snapshoted. So if boot is corrupted, you roll back. I should say I haven’t tried it though, to see how boot selection works (rolling back rpool is straightforward though).

The boot corruption could occur with the default file system ext4 also, except with ext4 there l is no recourse.

Needless to say, you can always boot from a live USB and mount your ZFS pool (and perhaps roll back).


I've had to recover a ZFS on root system, whose bootloader installation I had somehow screwed up, and the process is pretty straight forward.

See: https://openzfs.github.io/openzfs-docs/Getting%20Started/Ubu...


Isn’t ZFS there precisely to address your concern?!

If OS doesn’t boot, you boot from the latest snapshot! Every time you run apt-get upgrade, a system snapshots is taken automatically and an entry is added to boot menu.


I guess I was referring to more to corruption resulting in an unbootable system. If you can't boot in then how would you roll it back?


That's where backups come in. Any filesystem can get corrupted. Though for ZFS it's less likely than with something like ext4. Even though both have journalling, only ZFS has copy on write.


My problem was rather with problematic updates of zfs itself.

The update "helpfully" updated initramfs for older kernels too... and if something broke, it broke previous versions too, so they all were unbootable. Eventually I ended up with an USB stick at hand with known bootable environment :(




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: