NFS issues with 2.0

[TheLexus]

Hello there,

after updating to Beta 7 i get nfs errors (using the xbmc internal nfs) like this one:

19:02:48 T:140357417506560 ERROR: Failed to open(///) nfs_service failed
19:02:48 T:140357417506560 ERROR: GetDirectory - Error getting nfs://192.168.2.2//

This happens sometimes after resume. A "killall -9 xbmc.bin" helps in this situation. I cant tell exactly if Beta 6 has had the same issues but i had no issues with Beta 5.

The server is reachable, of course (verified by ping and manual nfs mount).

[Gummy35]

Had exactly the same problem on boot. All my thumbnails and config files are on NFS,
your post gave me the direction :

simply add the following line to your .config/autostart.sh

export XBMC_STARTDELAY="5000000"

The value for your system might vary, but it works on my zotac nd-22 .
May not solve the problem after resume however.

Seems like an over optimization of timings ...

-- EDIT :
Seems like a different issue. Sorry. It helped me solve the NFS at boot problem however.

[nmcaullay]

Hi there, I get problems with NFS when resuming from suspend in 1.95.7 (and have had this issue since 1.95.5). 1.95.4 seemed to restart XBMC upon resume, so the NFS connection issue was not obvious there.

A reboot fixes the issue, but hopefully we can figure out why SMB/NFS connections dont seem to work after resuming from suspend in OE.

related notes, a discussion on the OE forums
http://openelec.tv/forum/65-storage/44590-nfs-shares-missing-on-resume-1955-and-higher

A somewhat related issue in github
#1115

[TheLexus]

The problem seems to occur if the nfs server is rebootet during suspend of openelec. Maybe the nfs library must be reset to drop all connections... just a guess.

[nmcaullay]

I dont reboot my NAS between suspend of the OE machine, so while that maybe part of the problem, it isnt the whole thing.

[TheLexus]

I take a look at the xbmx git. The biggest change in relation to nfs since beta5 was inside NFSDirectory.cpp:

xbmc/xbmc@cfc20f6

The file NFSFile.cpp are not changed that much. I have not setup an build system at the moment (and no time to make one) but maybe someone can exchange the NFSDirectory.cpp file with the old version from beta4 and make a test build.

[nmcaullay]

A few other people have noticed that 1.95.4 tended to restart XBMC upon resume, which we thought might have resulted in NFS working. I think on the OE forum someone has a script hooked up to the "red" button to restart XBMC via remote once resumed, and it resolved the situation. So, potentially there is some issue to do with accessing remote NFS shares with XBMC immediately after it resumes. A reboot, or restarting XBMC seems to fix these poeples problems.

[TheLexus]

The problem is not fixed with 2.0 . Some poeple has noted that the problem occurs if oe was suspended a longer time (over night). On short resume cycles the prop will not raise that often.

We think the problem was the update of libNFS 1.3 (1.95.5).

[TheLexus]

OK, i tried to make a tcpdump for the dev of libnfs. BUT: There is NO nfs related traffic on the server if the error raises on openelec! Strange!

[guishark]

Hi,

i'm having similar issue with a Zbox AD10, using Openelec 2.0.

As a workoround, i use a power.restart script to restart xbmc on resume.

• Sometimes it works and i can access my media external HDD on resume,
• sometimes it works (xbmc resumes) but i cant access anymore the external HDD
• sometimes (usually after a long (a night) period of time) i just have a black screen

It is really anoying, hopefully someone will get a real fix since this have been spotted since 1.95.5

[jenkins101]

This is reported fixed in 3.0

duplicated issue.