NFS on 6.2rc2

[3blackdots]

Hi,

 

I am currently running 6.2rc2 and have a problem with my NFS shares. I realise that the initial post for 6.2beta18 indicated there was a problem with NFS and I can't say I have seen an updated post that says the problem has been fixed, however it works, but has some issues.

 

I have Kodi setup to access my media shares over NFS and for items already existing in the library it works fine, files are able to be played without issues. The problem lies with Kodi reporting folders as non-existent which means I can no longer scan new files into the library. This only occurs when accessing a user share, I can see and open the /mnt/user/Movies share but it is empty, but I tested exporting a disk share and then I am able to see all the sub-folders.

Kodi Log:
17:10:20 T:15600   DEBUG: NFS: Context for 192.168.1.54/mnt/user/Movies not open - get a new context.
17:10:20 T:15600   DEBUG: NFS: Connected to server 192.168.1.54 and export /mnt/user/Movies
17:10:20 T:15600   DEBUG: NFS: chunks: r/w 1048576/32768
17:10:20 T:15600   DEBUG: VideoInfoScanner: Scanning dir 'nfs://192.168.1.54/mnt/user/Movies/' as not in the database
17:10:20 T:15600   DEBUG: VideoInfoScanner: No (new) information was found in dir nfs://192.168.1.54/mnt/user/Movies/
17:10:20 T:15600 WARNING: VIDEO::CVideoInfoScanner::Process directory 'nfs://192.168.1.54/mnt/user/Movies/10,000 BC (2008)/' does not exist - skipping scan.
17:10:20 T:15600 WARNING: VIDEO::CVideoInfoScanner::Process directory 'nfs://192.168.1.54/mnt/user/Movies/12 Years a Slave (2013)/' does not exist - skipping scan.
...

 

I found a post in the past about possibly using NFSv4 for user shares and staying with NFSv3 for disk shares but that was about 2 years ago and I don't see any further posts to say this was actually implemented. I bring it up because the Kodi devs have indicated no plans to move to v4 support and wondering if this may be the cause of the issue?

 

I have gone and checked permissions on the folders and on the NFS shares but I can't see any problems:

cat /etc/exports

"/mnt/user/Movies" -async,no_subtree_check,fsid=101 *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash)
"/mnt/user/TV Shows" -async,no_subtree_check,fsid=100 *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash)

ls -l /mnt/user/Movies/

drwxrwxrwx 1 tony    users   44 Jan 23 16:03 007\ -\ Spectre\ (2015)/
drwxrwxrwx 1 tony    users   37 Jul 11 15:32 10\ Cloverfield\ Lane\ (2016)/
dr-xr-xr-x 1 nobody  users   44 Mar 27  2015 10,000\ BC\ (2008)/
drwxrwxrwx 1 nobody  users   34 Mar 27  2015 12\ Years\ a\ Slave\ (2013)/
...

 

I have tried changing various NFS parameters around, tried from windows, docker and raspberry pi versions of Kodi but all have the same issue and since they are able to access the server over NFS and can see folders on disk shares it makes me think it is something in unRAID stopping user shares exporting properly.

I have used the Movies share as an example here but it also happens on the TV Shows share as well (or whatever other share I try).

 

Has anyone else had the same problem or does anyone know what is going on here?

 

Thanks

tower-diagnostics-20160719-1655.zip