I decided to make a great update on network and server. OMV was on 3.x so ist was time to go ahead.
A clean installation was prefered, but after many hours of installation and configuration i realized, that NFS wasn't working.
Google couldn't help me and after two days i decided to ask the guys who know linux and OMV that much.
How to reproduce?
Download the latest image and make a fresh install of OMV (5.3.9).
After the installation (little hint to votdev: option for shutdown or reboot would be nice!) update all packages.
Install "sharerootfs" so you can make a share from the one and only drive of the server.
Add a shared folder without any permissions (everyone read/write). Apply and OK.
Go to NFS and enable the service (again apply and ok).
Add a share without any permission (clients: 172.168.0.0/16, rw, subtree_check, insecure <- default values) - apply and OK.
Reboot the server (or leave it and just try immediatly).
Login as root and try showmount:
showmount -e
-> /export/test1 172.16.0.0
-> /export 172.16.0.0
On a Windows 10 machine try:
showmount -e
-> out of time
If you try the following, all work fine:
showmount -e Server
-> /export/test1 172.16.0.0
-> /export 172.16.0.0
mount works fine:
mount -o anon \\Server\export\test1 z:
-> connected
Same behaviour on Linux and Android, but i am just a command-line-noob so i used KODI-Installations and tried to add sources. NFS browsing didn't work, the workaround throug zeroconfig works. Also a direct link to the source works (nsf://Server/export/test1).
I am not familar with nsf services, tried votdevs hints from another topic ("omv-salt deploy run nfs" and "omv-confdbadm read --prettify conf.service.nf"), but without errors (service already running and output looks like i configured the share) and it also did not solve the problem.
/etc/export looks good:
/export/test1 172.16.00/16(fsid=1,rw,subtree_check,insecure)
Any idea?
THX in advance