I know this is an old thread, but I thought I'd come back and post a solution that I eventually found to help others that may have similar issues.
I added the following to the Samba config file / extra options:
oplocks = no
level2 oplocks = no
aio read size = 1
I'm not sure if all options are required. I think the aio read size is the important one and may be the only option needed. In my case, it's a single server-client setup and the oplocks wouldn't make that much of a difference.
I don't know what happened but on the Estuary home page, my recently added icon for Movies and the titles icon is missing the text.
When I go into the Movies sub-menu, it shows "recentlyaddedmovies.xml" and "titles.xml" instead of the actual text. When i go into TVSHows submenu, similar thing. However, these menu items do work and show the correct list of Movies and TVShows.
The log shows these errors that seem to be related:
21:05:21.065 T:1857024928 ERROR: SQL: Missing result set!
21:05:21.128 T:1857024928 ERROR: GetMoviesByWhere failed
21:05:21.129 T:1857024928 ERROR: GetDirectory - Error getting special://skin/playlists/unwatched_movies.xsp
...
22:21:15.362 T:1944902096 ERROR: SQL: Missing result set!
22:21:15.362 T:1944902096 ERROR: GetMoviesByWhere failed
22:21:15.362 T:1944902096 ERROR: GetDirectory - Error getting library://video/movies/titles.xml/
22:21:15.376 T:1944902096 ERROR: CGUIMediaWindow::GetDirectory(library://video/movies/titles.xml/)I'm wondering if my SD card is going bad.
Is there a file I can look for to see if it actually exists and if so, what directory. I'm thinking that it's part of the standard LibreElec files that are installed and should exist.
Is there some way of overriding these files?
Just to add a few more details that I've come across and to note that I believe this is not an issue with LibreElec and most likely not addressable by Kodi either.
I've found other information that indicates the libnfs libraries used by Kodi may be causing issues. These are not Kodi libraries so they can't do anything about them. If that's the case, the best way to handle that is to pre-mount instead of using the built in Kodi mapping.
Additionally, I've determined that the Raspberry Pi is not helping this issue. I've also been trying to handle what I thought was a configuration issue with the MySQL database I set up. In the end it looks like Kodi is sending very large amounts of data, and that's another topic, and the slow Raspberry Pi wireless speeds are not helping. I'm going to be changing to PowerLine adapters, which I'm not currently using, that should help significantly.
With the new hardware, I've also upgraded to Linux Debian Stretch and to a more current version of OMV, 4.1.22, I believe.
In any case, as the problem does not happen when the drive is mounted before LibreElec Kodi starts and only happens if I use the drive/network browser to map the drive within LibreElec Kodi, I think that should be sufficient to identify where the issue exists. So, it may be newer versions of NFS have caused issues or specific options being used may have caused issues or it just may be something odd in my set up.
I've not had an issue with NFS before.
I tried with OMX and MMAL and with both off...same issue.
I am switching my network file server to new hardware and upgrading to a recent Linux and OpenMediaVault version. I use LibreElec on several Raspberry Pi 3's model B to access the file server. Version 8.25 and also tested with the current 9.x version, 9.01 I think.
I tried playing a video file from the new server and after a couple of minutes and when skipping around the video wildly...for testing purposes...the stream would stall and I would get various errors in the Kodi debug log. Kodi was still responding to key presses, but it hung waiting for the NFS mount.
In any case, while going through trying to identify the issue and then trying to test/view the NFS traffic between the client and server, I was setting up an external mount before starting Kodi so I could test different NFS options/configuration. Well, with the first thing i tried, specifying NFS version 3, it worked without issues. Only when using the built-in NFS and the Samba mounts did the issue occur. On my system/environment, it always happens with the built-in mapping.
The workaround is fine for me. I'm not sure if this is a specific LibreElec issue or a Kodi issue or may only specific to my environment. FYI, I tried this with the Krypton and Leia versions of LibreElec and also with an older Krypton version that was not LibreElec I had previously tested on a Linux Debian Jessie distribution on a Raspberry Pi. The issue happened on all of the versions.
Debug logs attached. One where it's using the NFS mount within Kodi, the other where it's mounted before Kodi starts and so you see /storage/nfs/SSD path references where the NFS drive is mounted to..
Another note, when using my old network file server, this issue does not occur.