(I realize my current TrueNAS Core build is not ideal for VM storage–they should be on NVME drives and I don’t have enough of those to use, for one.)
I’m running a test TrueNAS Core install (my first TrueNAS Core install) on a Dell Optiplex 5040 with 4x1.92 TB enterprise SATA SSDs for storage, in a single pool with two mirror VDEVs. Aside from creating it and making sure
ashift was set to 12 (the GUI doesn’t let you tweak this, so I was relying on it to be automatic), I haven’t tweaked the settings of the data storage pool in any way yet.
Aside from setting recordize and volblocksize attributes as necessary in my VM and CT storage datasets, are there any other attributes I need to change for remote Proxmox nodes on my LAN to use this storage? My goal is to set up the datasets, share them out to Proxmox, and not have to worry about tweaking them again.
- I’ve previously been using NFS on other nodes for accessing my backup server and the ISO storage on my QNAP, but I’m open to using CIFS if it would work better with TrueNAS Core.
- There are some things that I’d like to use iSCSI for, as well.
- There are also some settings used in Core that I don’t recognize from Proxmox/ZFS on Linux. The boot pool and my storage pool both use an
NFSv4, which I had never heard of before. I’m not sure if I need to change that if I’m going to use NFS and CIFS, or what impact it has on iSCSI.
- In addition to the above, is there anything else I need to tweak?