Appears to me that the NFS mount pointed at the wrong IP address. .2 but in the screen shot, it shows as .24.
NFS isn’t user-to-server authentication. It is server-to-server authentication with user’s getting native Unix file and directory permissions control. This means that having both the NFS client AND the NFS server with static IPs is the key part of the security. Of course, if you want more security, you can setup Kerberos trust between the systems, but that’s a hassle. If you want encrypted transfers, Kerberos is required. Basically, with normal NFS, there aren’t any user/password credentials exchanged without Kerberos (optional).
CIFS/Samba are user-to-server authentication with all the liabilities that includes.
I bet that
$ showmount -e xxx.xx.xx.2
would have shown the expected NFS service and any shared storage, if any are configured.
In OSMC, we can either mount storage using the OSMC GUI or let the operating system handle it. If we let the OS handle it, then OSMC doesn’t need to know anything about that and we just need to point at the directories like they were all local. This is how I do music to my OSMC playback devices. For video, I prefer to have a DLNA server (Jellyfin) provide the streams for TV, Movies, videos, and transcode to the format I want, when needed. Jellyfin runs on an x86-64 system with plenty of storage.
As for autofs … on the client side, there are 2 config files.
- /etc/auto.master
- /etc/auto.nfs
auto.master points at auto.nfs. We could name it anything, but using that name just for nfs mounts seems reasonable. The important line in auto.master should look like this:
/- /etc/auto.nfs
Inside auto.nfs, I have mounts like this:
/d/D1 -fstype=nfs,nconnect=4,proto=tcp,rw,async istar:/d/D1
/d/D2 -fstype=nfs,nconnect=4,proto=tcp,rw,async istar:/d/D2
/d/D3 -fstype=nfs,nconnect=4,proto=tcp,rw,async istar:/d/D3
Under each of those different file systems, I have TV, Movies, Video directories. So, when I setup the TV library, there are 3 lines …
- /d/D1/TV
- /d/D2/TV
- /d/D3/TV
and OSMC merges all the content for me.
Of course, backups for each of those file systems are in
- /d/b-D1/TV
- /d/b-D2/TV
- /d/b-D3/TV
I didn’t want to confuse myself. I originally started with /d/D1 … and added content until it was full. Then I added D2 … D3 and at this point, I’m removing content to make room for new stuff.
I also go out of my way to mount the NFS storage in the same place it resides on the NFS server. Again, this is to limit my confusion when I’m working on different systems. The NFS server is also where Jellyfin runs. I don’t have a dedicated NAS box. My NFS server is just another Linux system here.
Updates: Struck out the initial, incorrect, statement. Corrected showmount IP address. Decided to leave this post for future lurkers to see autofs, gain a little NFS config examples and consider some options and choices to allow more storage to be added.