+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: NFS source in Eden with NFSv4 (/showthread.php?tid=128682)
NFS source in Eden with NFSv4 - cyberwizzard - 2012-04-12
Is it possible to add an NFSv4 source to Eden? I do not care for auto-mounts or similar, I want to add it as a direct source using a URI like "nfs://myip/shares".
I found that Eden natively supports NFS and I can find my home server from the "Add Source" panel, I just can't enter the share - it remains empty even though the machine I'm trying it on can access the shares just fine. Also, the article on the wiki does not mention if there is a restriction on the NFS version.
NFS source in Eden with NFSv4 - Memphiz - 2012-04-13
post xbmc.log
RE: NFS source in Eden with NFSv4 - vicbitter - 2012-04-13
I am using NFSv4 on my NAS and I have Eden running on ATV2 and an ION HTPC. Both can access the shares without any problem so it maybe an authorisation issue, etc.
As Memphiz said can you post your xbmc.log.
RE: NFS source in Eden with NFSv4 - cyberwizzard - 2012-04-13
Cheers, at least I now know it should work.
I'll keep digging and post the logs if I can't figure it out.
RE: NFS source in Eden with NFSv4 - cyberwizzard - 2012-04-14
I tried again and I still can not get it to work. The computer that I'm trying this on has auto-mounts (which I disabled to see if it mattered) which require no special UID or other custom stuff - just mount and go.
When I try to do the same in XBMC, I see that the auto-detection comes up with a different path than my fstab has. I tried both 'nfs://ip/exports/videos' and 'nfs://ip/videos' (the latter being the same as fstab) and nothing works. The first shows a blank list, the second an error it can not connect to the server.
Log:
Code:
00:40:10 T:139965541918592 DEBUG: ------ Window Init (MyVideoNav.xml) ------
00:40:10 T:139965541918592 INFO: Loading skin file: MyVideoNav.xml
00:40:11 T:139965541918592 DEBUG: CGUIMediaWindow::GetDirectory (sources://video/)
00:40:11 T:139965541918592 DEBUG: ParentPath = [sources://video/]
00:40:11 T:139964260022016 DEBUG: Thread Background Loader start, auto delete: 0
00:40:11 T:139964260022016 DEBUG: Thread Background Loader 139964260022016 terminating
00:40:12 T:139965541918592 DEBUG: ------ Window Deinit (DialogKaiToast.xml) ------
00:40:12 T:139965541918592 DEBUG: ProcessMouse: trying mouse action leftclick
00:40:12 T:139965541918592 DEBUG: ParentPath = [sources://video/]
00:40:12 T:139965089322752 DEBUG: SECTION:LoadDLL(libnfs.so.1)
00:40:12 T:139965089322752 DEBUG: Loading: libnfs.so.1
00:40:12 T:139965089322752 DEBUG: NFS: Context for 192.168.2.5/mnt/exports not open - get a new context.
00:40:12 T:139965089322752 DEBUG: NFS: Connected to server 192.168.2.5 and export /mnt/exports
00:40:12 T:139965089322752 DEBUG: NFS: chunks: r/w 262144/32768
00:40:12 T:139964260022016 DEBUG: Thread Background Loader start, auto delete: 0
00:40:12 T:139964260022016 DEBUG: Thread Background Loader 139964260022016 terminating
00:40:13 T:139965541918592 INFO: LIRC Initialize: using: /dev/lircd
00:40:13 T:139965541918592 DEBUG: Failed to connect to LIRC. Retry in 20s.
00:40:13 T:139965541918592 DEBUG: ProcessMouse: trying mouse action leftclick
00:40:13 T:139965541918592 DEBUG: CGUIMediaWindow::GetDirectory (sources://video/)
00:40:13 T:139965541918592 DEBUG: ParentPath = []
00:40:13 T:139964260022016 DEBUG: Thread Background Loader start, auto delete: 0
00:40:13 T:139964260022016 DEBUG: Thread Background Loader 139964260022016 terminating
00:40:14 T:139965541918592 DEBUG: ProcessMouse: trying mouse action leftclick
00:40:14 T:139965541918592 DEBUG: CGUIMediaWindow::GetDirectory (nfs://192.168.2.5/videos/)
00:40:14 T:139965541918592 DEBUG: ParentPath = [sources://video/]
00:40:14 T:139965541918592 ERROR: GetDirectory - Error getting nfs://192.168.2.5/videos/
00:40:14 T:139965541918592 ERROR: CGUIMediaWindow::GetDirectory(nfs://192.168.2.5/videos/) failed
00:40:14 T:139965541918592 DEBUG: CGUIMediaWindow::GetDirectory (sources://video/)
00:40:14 T:139965541918592 DEBUG: ParentPath = []
00:40:14 T:139965541918592 INFO: Loading skin file: DialogOK.xml
00:40:14 T:139964260022016 DEBUG: Thread Background Loader start, auto delete: 0
00:40:14 T:139964260022016 DEBUG: Thread Background Loader 139964260022016 terminating
00:40:14 T:139965541918592 DEBUG: ------ Window Init (DialogOK.xml) ------RE: NFS source in Eden with NFSv4 - Memphiz - 2012-04-14
See the wiki entry and see that "insecure" flag which is needed (for e.x. linux servers its insecure flag, for osx servers its the -N flag in the plist). Looks like your server doesn't allow connections from non-privileged ports. This is needed for getting the internal XBMC NFS client to work.
RE: NFS source in Eden with NFSv4 - cyberwizzard - 2012-04-15
I just checked but I already have the insecure flag set for each of my exports.
NFS source in Eden with NFSv4 - Memphiz - 2012-04-15
and you restarted the nfs server after adding the insecure flag? beside that - post a full log to pastebin.com and put the link to it here...
RE: NFS source in Eden with NFSv4 - cyberwizzard - 2012-04-25
The insecure flag was already there.
I now have it working after removing the root of the pseude-filesystem:
Quote:/mnt/exports 192.168.1.1/16(rw,fsid=0,insecure,no_subtree_check,async,all_squash,anonuid=1001,anongid=1001)
/mnt/exports/series ....
I added this line by following pretty much any guide on NFS mounts as all of them include it. None of the guides actually explain why it is needed, except for the Red Hat guide which mentions the 'fsid=0' denotes that it is the root of the pseudo-filesystem.
Why do I need to disable it and if I do not need it, why does everyone with an NFS server seem to have it?
RE: NFS source in Eden with NFSv4 - Memphiz - 2012-04-26
You mean fsid=0? Well this seems to be a NFSv4 specification. But i don't really get why this is needed. I think this is only interesting if you export from different physical drives and want to ensure that these are really mounted (so not the underlaying root fs is exported when the mount fails).