Messages

Hmm.. UFS is a no-go then, since the server is currently susceptible to brownouts/blackouts with no UPS (working on that)

I think I can bump that VM to 4GB since I retired a couple of VMs a while ago so I think I have the memory to spare.

Would OPNsense being tight on memory cause the checksum errors? Because I suspected this might be the case, I'm now testing with an 8GB swap on the boot SSD, separate from the ZFS array

Any drawbacks to doing OPNsense on UFS compared to ZFS? I remember reading that ZFS is the "recommended" filesystem for OPNsense, but I understand that this recommendation comes with the assumption that OPNsense is running bare metal. And yes I don't do ZFS on anything but bare-metal, but went with the default for OPNsense.

I have been running OPNsense at home on my home server for a while now. OPNsense is virtualized using KVM/QEMU with 2 vCores, 2GB RAM, 20GB VirtIO disk, and a dual-NIC Gigabit intel PCIe card passed through.

I have a big issue with ZFS-on-ZFS where the main data array consists of 3 2TB HDDs in a Z1 configuration, and OPNsense lives on top.

The issue:

Running weekly scrubs on the main data array eventually accumulates checksum errors, and the OPNsense VM completely fails. It's always the OPNsense VM media that the main array complains about, and eventually show as the source of unrecoverable errors.

What I tried:
* Using ZVols
* Using a regular qcow2 device
* Disabled all logs/metrics (Unless there's something I'm missing)
* Moving the swap partition off of the ZFS array and putting it on the boot SSD, as well as enabling auto-trim (Testing in progress)

Although I have close to a decade of professional experience with Linux, I'm pretty much a beginner when it comes to the BSDs.

Bare-metal runs NixOS if that's relevant.