Unable to add new NFS share

    Hi.

    First, yes, i saw the slightly older Thread regarding NFS/SMB...but as i do not want to connect with smb and nfs was not further mentioned in it.

    To get a bit started....currently running the nightly build 20260509-889687c on a pi5 (4GB) and noticed that every build after causes the pi to crash in less then a minute (cpu gets loaded over 100% and ram usage jumps per second) .

    I already identified that it most likely is an addon or settings problem, as it seem to run fine when i do a clean install with a current build.

    The problem now, for some reason i can not add the NFS shares where i store my Music/Videos and so into the system (or i do something wrong without realizing it)...regardless of it being the clean build, or the currently used one. It is not a problem to access the existing NFS Links which got added ages ago.

    Anyone can see what might be the problem with that?

    Wanted to upload the log trough libreelec, but only got an error so i hope i got the correct file. it is a bit large as there seem a lot jumps for scanning files in it, but the nfs tries should be the ones towards the end of it.

    kodi.log

    Small Update.

    Librelec/kodi stil goes haywire if updated and cant add any nfs stuiff at all.

    Did a dirty solution:

    Installed the current nightly clean, created a backup, switched the sources.xml (and the database stuff for videos, so that i keep the watched stats) from the working installation into the clean backup and imported that.

    At least i can now access the files from there, and at least know that neither the media database or the sources.xml was the cause for the overload & crash........but still would want to know the cause why i cant create/access new nfs shares......

    for me I got trouble to understand what you're trying to archive esp. how you tried to do it.

    you know NFS is a client/server protocol, where a server exports directories and a client mount them.

    when I read your "trying to create a share or something like that" it sounds to me you're all doing it on the client side.

    - I might be wrong -

    ===

    to your problem:

    grepping after nfs throught your log gives me:

    Code
    2026-05-24 14:18:55.876 T:1210    debug <general>: NFS: version: 3
2026-05-24 14:18:55.881 T:1210    debug <general>: NFS: Connected to server 192.168.178.6 and export /volume1/Backup
2026-05-24 14:18:55.881 T:1210    debug <general>: NFS: chunks: r/w 131072/131072
2026-05-24 14:19:01.563 T:985   warning <general>: FileNFS::OpenForWrite() called with overwriting enabled! - //Backup kodi/kodi.log
2026-05-24 14:19:04.591 T:985     debug <general>: CNFSFile::Close closing file volume1/Backup/Backup kodi/kodi.log
2026-05-24 14:19:25.366 T:1271    error <general>: GetDirectory - Error getting nfs://
2026-05-24 14:19:25.395 T:955     error <general>: CGUIDialogFileBrowser::GetDirectory(nfs://) failed
2026-05-24 14:19:27.332 T:1273    error <general>: GetDirectory - Error getting nfs://
2026-05-24 14:19:27.361 T:955     error <general>: CGUIDialogFileBrowser::GetDirectory(nfs://) failed

    - first line: "NFS Version 3":

    AFAIK and according to the LE wiki it should be version 4 (if your NFS server could talk version 4 !)

    - last line:

    asking google with "GetDirectory - Error geeting nfs://" told me something like "the directory your client tried to mount does NOT exist or is NOT reachable on the server"

    ===

    my way I would investigate such an problem would be via cmdline:

    - create on the NFS server the share

    - ssh into your client

    - create a temporary directory for an mount point with "mkdir -p /storage/NFSSHARE"

    - from the client try to mount the share with something like the following command:

    mount.nfs -v -o soft,intr 192.168.200.24:/home/DATA/SHARE/ /storage/NFSSHARE

    ADJUST before:

    - the IP Adress of the NFS server (in my example: 192.168.200.24)

    - the share, what the NFS server exports (in my example: /home/DATA/SHARE/)

    it doesn't hurt to reboot the NFS server or to restart the NFS service that the the server is full aware of the new share ...

    - and where to mount the share (in my example: /storage/NFSSHARE)

    ===

    one could open a 2cd ssh connection and run in that terminal "journalctl -f" what lists what the above mount command generates as messages/errors

    if errors: google with the complete error string

    if NO errors try to read the mounted directory with : ls -l /storage/NFSSHARE/

    ===

    your log seems to be full of junk regarding of an non-existing directory "/Musik/YABACUBE INC/"