NFS-Changes in newest release? Can't access NFS-share from KODI on Android-TV

tsch · Nov 27th 2025

After upgrading to the newest version of OMV 7.x I can't access the nfs share on my OMV 7 NAS.

Any changes and hints how to make the share available from my android-tv via KODI?

votdev · Nov 27th 2025

How does your /etc/exports look like?

It may now be the case that the configuration that was previously working was actually incorrect and has now been created correctly, but this has resulted in the opposite situation.

tsch · Nov 27th 2025

This is my etc/exports:

Code

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.


# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
/export/OMV7-02 192.168.178.0/24(fsid=9608d0ca-2b34-4268-9fd0-50c21a573b13,rw,subtree_check,insecure)
/export 192.168.178.0/24(ro,fsid=0,root_squash,subtree_check,insecure)

votdev · Nov 27th 2025

Nope, i don't think the latest changes are causing this because the only thing that was fixed was that under some special circumstances the line

Code

/export 192.168.178.0/24(ro,fsid=0,root_squash,subtree_check,insecure)

could mistakenly look like this

Code

/export 192.168.178.0/24(ro,fsid=0,root_squash,subtree_check,ininsecure)

This was fixed; nothing more.

tsch · Nov 28th 2025

Thanks votdev.

So I have to check if there where any changes in KODI.

molnart · Dec 30th 2025

i have noticed the same issue after updating to OMV 8 - my NFS shares were empty on all my clients.

realized that i had to remove the subtree_check from all the shares to show up on the clients.

Also not sure if related, but the showmount -e command does not seem to work since OMV 8. i am just getting a clnt_create: RPC: Program not registered error.

ryecoaaron · Dec 30th 2025

It must be something else. my system upgraded from omv7 isn't having a problem with nfs shares and I just setup a new nfs on a fresh omv8 system and it works fine.

Code

# cat /etc/exports
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.


# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
/export/scripts 192.168.1.0/24(fsid=531b00ca-afcf-4f08-b515-9ff0e76394a4,ro,subtree_check,insecure)
/export 192.168.1.0/24(ro,fsid=0,root_squash,subtree_check,insecure)

showmount works as well.

Code

$ sudo showmount -e omv8test
Export list for omv8test:
/export         192.168.1.0/24
/export/scripts 192.168.1.0/24

Quote from molnart

realized that i had to remove the subtree_check from all the shares to show up on the clients.

if you add it back now, do they work?

gderf · Dec 30th 2025

I'm on OMV 8 and showmount -e works for me. I also still have subtree_check enabled and have no problems with NFS.

molnart · Dec 30th 2025

i forgot to mention i am on ZFS. so maybe this is somehow related to how the ZFS datasets are served to NFS?

Quote from ryecoaaron

if you add it back now, do they work?

no, they stop working again. i also tried removing the NFS shares and re-adding them (had to do it in the past a few times) but did not help until i removed the subtree_check param

also realized showmount is not even working when executing locally on the OMV host.

This is my /etc/exports file. Not sure where those last 3 lines are coming from

Code

/export/Images 192.168.50.0/24(fsid=949dfd02-f8d3-4218-9718-bb0b12f83354,rw,subtree_check,insecure,sync,crossmnt,no_root_squash)
/export/Camera 192.168.50.0/24(fsid=66488731-3e06-4764-8f88-2429c77d3193,rw,insecure,crossmnt)
/export/Backups 192.168.50.1/24(fsid=a4030be9-ace3-46cc-a885-524df59276d0,rw,async,no_wdelay,crossmnt,insecure,no_root_squash,insecure_locks)
/export/downloads 192.168.50.60/24(fsid=124d3cce-0e98-4d05-bd04-148fcb43047b,rw,insecure,crossmnt,insecure_locks,no_root_squash)
/export/Movies 192.168.50.60/24(fsid=69037c28-3b71-4df8-9ec9-b21a97c22d31,rw,insecure,crossmnt)
/export/Music 192.168.50.60/24(fsid=3bdd7c74-3e29-436e-91a1-fe3a9e5cee22,rw,insecure,crossmnt)
/export/Documents 192.168.50.60/24(fsid=001c6e95-38bb-442f-bf29-2f57bf094729,rw,subtree_check,insecure,crossmnt)
/export/Photos 192.168.50.60/24(fsid=1b43221a-8b63-4079-b8cb-a49f47f03d3c,rw,insecure,crossmnt)
/export/various 192.168.50.0/24(fsid=170572e0-d5c9-4160-a0f1-559a43560ce7,rw,subtree_check,insecure,crossmnt)
/export 192.168.50.0/24(ro,fsid=0,root_squash,subtree_check,insecure)
/export 192.168.50.1/24(ro,fsid=0,root_squash,subtree_check,insecure)
/export 192.168.50.60/24(ro,fsid=0,root_squash,subtree_check,insecure)

Display More

ryecoaaron · Dec 30th 2025

Quote from molnart

i forgot to mention i am on ZFS. so maybe this is somehow related to how the ZFS datasets are served to NFS?

From what I can find, subtree_check is not recommended for zfs. Do you need it?

molnart · Dec 30th 2025

nope, i don't think so. i was just wondering why this happened, since it was working on 7.x and saw a similar thread, so i though it might be related

ryecoaaron · Dec 30th 2025

newer kernel and zfs versions might have something to do with it.

Participate now!