Can you explain your use case when you absolutely can't provide a separate M.2 drive solely for the OS?
It is unlikely for there to be issues with ZFS and Linux. It's too common now, but it's not included in the main Linux tree, so it's not explicitly tested.
So, it's a low risk, but not zero risk.
More to the point here, when working with FreeBSD, ZFS is a first-class citizen (moreso even), so working with it *should* be more integrated with a FreeBSD solution than Proxmox, but how much more (and is that meaningful) is probably a qualitative feel than quantitative fact.
There have since been implementations for Linux but no distribution is designed to support them.
Folks using TrueNAS or unRAID for backup instead of safe keeping, and then get mad when everything goes sideways and the data is gone. Your NAS must have a backup elsewhere, snapshot and what not won't save you if everything goes RIP.
ZFS is redundancy and redundancy only, but people see ZFS as some sort of backup. That is silly and wrong.
>A rollback capability is why I'm looking for Proxmox alternatives.
Your VMs and LXC container should have an automated backup. Proxmox itself takes a second to clean install it.
I had to change the motherboard and had to literraly install Proxmox 9.1 from scratch. BUT.... before doing that, I checked the LXC backups sent to a TrueNAS spool in mirror for safe keeping.
Reinstalled Proxmox, mounted the NFS share on Proxmox and voila, all the LXC containers were restored and started like nothing happened.
I'm talking about this, basically: https://www.linuxquestions.org/questions/*bsd-17/howto-zfs-m...
There have since been implementations for Linux but no distribution is designed to support them.