by ceejayemm » 03 Sep 2020, 08:40
Andy
I use NFS as a matter of course when possible to connect to my NAS (OMV v5.x) where my music is stored. I have been doing this ever since I started using RA 0.2/0.3 four or five years ago and I DON'T think NFS itself is the issue. I don't specify the NFS mount options specifically but RA shows the mounted share with the following options anyway (some of which seems overkill to me):
rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=5,retrans=2,sec=sys,mountaddr=192.168.86.250,mountvers=3,mountport=35748,mountproto=udp,local_lock=none,addr=192.168.86.250
The problem seems to be that, when the Library gives the message 'No Data in This Location. Update for changes then try again', the actual mount point is missing, when I do df -h, I only have the local mount point available to me. A reboot invariably solves the problem. I have been using the hostname of my NAS server, rather than its IP Number, and I think that Arch-Linux is sometimes having problems resolving the hostname via my local DNS server which I have posted about elsewhere in this forum. I was always told by networking experts where I used to work that hostnames should be used wherever possible to give the best flexibility to the network and have been using that adage (hostnames, fully qualified domain names etc) all my working life in computers and now continue with it at home. Last night I reluctantly reverted to an IP Number for this particular RA installation and I am now waiting to see what happens with this setup when a reboot is necessary.
I am having similar NFS mount problems with other newer installations of Linux (Debian, Ubuntu and Rasbian) elsewhere and have resorted in these cases to use autofs which seems to mount the NFS shares more reliably and automatically includes a timeout when the NFS share is not in use.
Chris