Intel Xeon, 4GB RAM, VM, openSUSE Linux.
Music library on external NAS, mounted on core machine using NFS
Number of Tracks in Library
~20k tracks
Description of Issue
I recently migrated my roon core machine to a linux VM. Everything works fine, except my library will not auto-update. It will update if I force a scan, but will not automatically. I am wondering if this has something to do with my library being a mounted NFS share? Does roon have issues with NFS on a linux host?
It has unlikely to do with Roon. Roon doesn’t know that this directory is a mounted NFS share instead of a normal local folder. Mounting directories is the responsibility of the OS in use, as well as real-time watching for changes (note: for remote shares it may also be the responsibility of the remote share host). Roon as a userland process can just request this service from the OS. If Roon doesn’t get informed about changes as requested, Roon can’t do anything about it.
Maybe it’s just a too low max_user_watches? Maybe it’s an known NFS limitation? Or something SUSE related?
Then Roon has the expected rights to access the folder and all is well in this regard. While Roon does perform a scheduled rescan of remote (SMB) shares setup as watched folders in Roon, this is AFAIK not done for local folders (or a remote share that Roon thinks is a local folder).
Note: Not a supported installation method. Finding and fixing problems that may result or arise thereof are to be resolved by the tinkerer who set this up. Fixing general OS and setup (storage, mounts, real-time watching) related issues is the job of the responsible system administrator.
There is a Tinkering section on this forum for tinkering related questions where you might get support by other users. I don’t think that Roon Labs support is able to help you with your specific, non Roon related issue here.