Comment on NixOS and/or TrueNAS - What are your experiences?
philpo@feddit.org 2 days agoThe question is why. TrueNAS adds a lot of overhead, tends to become unstable if the workload is high in a VM, can lead to problems especially with ZFS and it often leads to people using privileged containers to use NFS directly (for ease of use) or use a mount bind solution via the host.
With ZFS NFS the whole thing can easily be provided directly and then use mount bind - which is way more consistent. With Cockpit and Napp-it you have graphical tools available.
Don’t get me wrong, for an existing solution it’s fine,but if one is doing a new build I would absolutely not go for it.
monkeyman512@lemmy.world 2 days ago
My setup is very influenced by consolidating multiple hosts to a single host. So far this setup has been extremely stable for me with the only quirk being the Truenas web gui initially loads very slowly if I haven’t accessed in a couple days. I assume it’s because all the memory for that has gone to swap to make space for caching.
philpo@feddit.org 2 days ago
Yeah, I come from the same scenario. Consolidated multiple nodes incl. a NAS into one. Initially had the HDD (which run through a controller anyway) passed through to a TrueNAS VM. That was…a mistake. TrueNAS can become a real bitch if it’s own VM storage is slower/has a hiccup while the rest of the pool is not. And a lot of other things are a PIA as well, e.g.permission wise, especially with a FreeIPA Domain. And all that for a quite hefty price in ressources.
The day I pulled the plug on that was a good day. Later had the issue repeat itself with a client system that the client brought with him.
Nowadays I really love the proxmox only solution,even though it’s somewhat icky to run something directoy on the host - but it’s acceptable imho,when it’s literally built onto host data-as it is the case for ZFS NFS anyway.
(I have Samba in a proper LXC, though - but rarely use it these days as we run everything via NFSv4 by now)