vitaprimo
Dabbler
- Joined
- Jun 28, 2018
- Messages
- 27
I'm installing FreeNAS as an app server. It's virtualized with the tiniest virtual disk, just enough to keep the plugins' images, config, incomplete and/or data being processed because I'd like to use object storage shares from other servers to store the rest--all of the super advanced features of ZFS are counterproductive on a virtual disk, already with plenty overhead/abstraction from vSAN.
I'd like to mount the shares and map them right in the filesystem so they become available for selection in a plugin or jail's settings like any other dataset would but I'm not exactly sure how to achieve this.
Normally on Linux systems, I would use Cockpit to do its magic deep down the system settings while being non-invasive. Cockpit sets fstab entries and makes sure links to remote servers don't go stale (and then things fail) but, there's no Cockpit for FreeBSD and I just read somewhere in here (the forum) that FreeNAS rewrites fstabs on reboot as a fail-safe (I assume) and I'm not skilled enough (at all) to set the parameters for hard/soft mounts and the retry values and all those things so it won't fail.
Going through the docs I found out about Pre Init Tasks, it seems like a good place to start but I'm blanking out on the rest. Could you guys point me in the right direction? Or maybe tell me if this is possible at all?
I have available NFS3, NFS4.1*, SMB2** and SMB3** shares to mount in FreeNAS. FreeNAS has already joined the domain. I would rather go with NFS3 because it's the easiest but I'll take any advice. I'm using vSphere for the virtual environment.
Thanks.
*: with/without auth_sys, Kerberos auth, Kerberos integrity and Kerberos encryption
**: on Active Directory domain
I'd like to mount the shares and map them right in the filesystem so they become available for selection in a plugin or jail's settings like any other dataset would but I'm not exactly sure how to achieve this.
Normally on Linux systems, I would use Cockpit to do its magic deep down the system settings while being non-invasive. Cockpit sets fstab entries and makes sure links to remote servers don't go stale (and then things fail) but, there's no Cockpit for FreeBSD and I just read somewhere in here (the forum) that FreeNAS rewrites fstabs on reboot as a fail-safe (I assume) and I'm not skilled enough (at all) to set the parameters for hard/soft mounts and the retry values and all those things so it won't fail.
Going through the docs I found out about Pre Init Tasks, it seems like a good place to start but I'm blanking out on the rest. Could you guys point me in the right direction? Or maybe tell me if this is possible at all?
I have available NFS3, NFS4.1*, SMB2** and SMB3** shares to mount in FreeNAS. FreeNAS has already joined the domain. I would rather go with NFS3 because it's the easiest but I'll take any advice. I'm using vSphere for the virtual environment.
Thanks.
*: with/without auth_sys, Kerberos auth, Kerberos integrity and Kerberos encryption
**: on Active Directory domain
