[jmgibson1981]

https://paste.ubuntu.com/p/9xPMwDPyJD/

I recently changed my main server to Debian from Ubuntu. I am using LXD to serve up my ubuntu containers, including ltsp pxe booted kodi machines. All kodi machines are Ubuntu. Something is different about Debian's nfs share as I can no long add shares through add videos, I'm guessing other ways as well. What is interesting is that all my other existing shares already in place from my mariadb database all play just fine. They can see the nfs share perfectly. I just can't add a new share. Log just says it can't find nfs. Errors out. Here are my nfs share config files as well. I'm not sure what if anything is different from ubuntu.

For the moment I have my new shares mounted through an autofs mountpoint into the ubuntu machines. But I'd prefer a regular nfs mount for many reasons.

I removed commented lines for brevity. The exports file was directly copy pasted from ubuntu to debian file. The fsid is required for mergerfs.

Code:

cat /etc/exports
/snapraid/pool          192.168.1.0/24(rw,insecure,no_root_squash,no_subtree_check,fsid=2)

 

Code:

cat /etc/default/nfs-kernel-server 
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""

 

Code:

apt policy nfs-kernel-server
nfs-kernel-server:
  Installed: 1:1.3.4-2.5
  Candidate: 1:1.3.4-2.5
  Version table:
 *** 1:1.3.4-2.5 500
        500 http://deb.debian.org/debian buster/main amd64 Packages
        100 /var/lib/dpkg/status

[DaVu]

I can't browse my NFS shares anymore as well. Using UnRaid in this case. You have to add your NFS via the "Add network location" and fill out the dialog with the specific entries (ip, path to share etc.).

At least that's how it works for me.

I already opened an issue at libnfs, but it seems that it's UnRaid which is causing the issue.

[Klojum]

I lost NFS browsing on Ubuntu and Windows clients, but it does still work in LibreELEC surprisingly enough.

Alternatively you could add/edit your sources.xml file, or use system-based NFS shares and have Kodi pick up those.

[jmgibson1981]

I lost NFS browsing on Ubuntu and Windows clients, but it does still work in LibreELEC surprisingly enough.

Alternatively you could add/edit your sources.xml file, or use system-based NFS shares and have Kodi pick up those.

I opted to mod the sources.xml directly. Just copy pasted, then adjusted to what I needed them to be. I'm glad adding sources isn't a regular thing to do or this could be an issue. Thank you for all replies. I'm not sure if I should mark solved or not as the main issue persists.

[asavah]

I already opened an issue at libnfs, but it seems that it's UnRaid which is causing the issue.

Don't think it's just unraid, Ubuntu is also affected, I have my own gnu/linux OS (client) with both Kodi and libnfs built from git master and I can't see my NFS exports from my Ubuntu 19.10 server via Kodi gui through add dialog,
showmount -e serverip lists everything tho, not an issue for my personal usecase as I use fstab mounts, but it would be intresting to fix this.

https://github.com/sahlberg/libnfs/issues/294 from what I gather from the issue it's nfs server configuration issue, it does not respond to rpcinfo broadcasts.
I'll try to find the knob/patch responsible for this.

EDIT: It's rpcbind issue, remote calls were disabled by default and sadly it's a compile time option, not possible to enable this without rebuilding
https://github.com/sahlberg/libnfs/issue...-426762673
https://sourceforge.net/p/libtirpc/mailm.../36377522/

[DaVu]

at least there's an open bug for it and I already posted there as well. Limetech flagged it with "minor". So it's not "not a bug"

https://forums.unraid.net/bug-reports/st...-nfs-r551/

The issue on libnfs was also reproduced by milhouse with a different raid system. And as Salberg said: "Actually, Unraid no longer support mount version 2." which might be the issue for me.

also not a biggy for me, as I can add those shares in multiple ways. But it's not that user-friendly.

[Nightah]

at least there's an open bug for it and I already posted there as well. Limetech flagged it with "minor". So it's not "not a bug"

https://forums.unraid.net/bug-reports/st...-nfs-r551/

The issue on libnfs was also reproduced by milhouse with a different raid system. And as Salberg said: "Actually, Unraid no longer support mount version 2." which might be the issue for me.

also not a biggy for me, as I can add those shares in multiple ways. But it's not that user-friendly.

Sorry I'm still a little confused by this statement, are we saying there's an issue in in libnfsthat needs to be resolved?

Following the chain the original issue was someone running Arch Linux as the NFS server and explained that rpcbind didn't have that compile flag enabled. This was later updated on the 28th of October, I'm also running Arch and experience the same problem that I cannot browse NFS shares with the nfs:// prefix.

I'm using LibreELEC and it appears the issue manifested in 9.1.502 and is also present in 9.2.0 Kodi, rolling back to 9.1.501 seems to workaround the issue in the interim.
Should I be lodging this issue downstream for LibreELEC?

[jmgibson1981]

at least there's an open bug for it and I already posted there as well. Limetech flagged it with "minor". So it's not "not a bug"

https://forums.unraid.net/bug-reports/st...-nfs-r551/

The issue on libnfs was also reproduced by milhouse with a different raid system. And as Salberg said: "Actually, Unraid no longer support mount version 2." which might be the issue for me.

also not a biggy for me, as I can add those shares in multiple ways. But it's not that user-friendly.

Sorry I'm still a little confused by this statement, are we saying there's an issue in in libnfsthat needs to be resolved?

Following the chain the original issue was someone running Arch Linux as the NFS server and explained that rpcbind didn't have that compile flag enabled. This was later updated on the 28th of October, I'm also running Arch and experience the same problem that I cannot browse NFS shares with the nfs:// prefix.

I'm using LibreELEC and it appears the issue manifested in 9.1.502 and is also present in 9.2.0 Kodi, rolling back to 9.1.501 seems to workaround the issue in the interim.
Should I be lodging this issue downstream for LibreELEC? 

Don't know where to issue it as that is out of my scope. To much noob. I do know that my problem is on an Ubuntu 18.04 installation via ppa. I don't use *ELEC.

[fritsch]

NFS browsing works nicely for me. Android + Ubuntu 18.04 nfs shares.

[DaVu]

Yes, that's known that it works if the host OS is Ubuntu. If your host is something like UnRaid it doesn't work. I already commented on an open bug at unraid, but I guess there will not be much progress. They flagged it as a "minor" bug. Nothing to worry about as one is still able to shares via

- the "add network location"-option
- the OS via system mounts

It's a bit unfortunate that it has become harder for some ppl.

[Nightah]

I don't know that this is just limited to the Host OS.
Given that in my case underlying host OS and NFS server setup is the same, the moment I change the version of LibreELEC it stops working and rolling back with no other changes results in working Kodi again.