No NFS mount possible

Peronia · 17. April 2024

Hi,

today I upgraded from OMV 6 to OMV 7, without problems.

Now my servers can't connect via NFS. with showmount --exports uranus I am able to see the shares:

Code

root@miranda:~# showmount --exports uranus
Export list for uranus:
/export/Switch    192.168.230.0/24
/export/Software  192.168.230.0/24
/export/Dokumente 192.168.230.0/24
/export/Medien    192.168.230.0/24
/export/Downloads 192.168.230.0/24
/export/Backup    192.168.230.0/24

BUT the specific NFS mount for that client (miranda) doesn't show up. Here 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/Backup sonne(fsid=13e8c527-d2b0-4dde-85ea-8a121a05f4db,rw,subtree_check,insecure,all_squash,anonuid=1001,anongid=1002) 192.168.230.0/24(fsid=92993a13-490d-4a9d-8114-5f18c4f2bb6d,rw,subtree_check,insecure,all_squash,anonuid=1000,anongid=1002)
/export/Dokumente 192.168.230.0/24(fsid=c27fe697-e226-44a3-ae7e-0148285512e8,rw,subtree_check,insecure,all_squash,anonuid=1000,anongid=1003)
/export/Downloads miranda(fsid=382ec001-4514-4023-a22b-f2257f89d037,rw,subtree_check,insecure,all_squash,anonuid=1003,anongid=1001) 192.168.230.0/24(fsid=c81c9d91-0469-4d0b-a5b8-322d6138f2ad,rw,subtree_check,insecure,all_squash,anonuid=1000,anongid=1001)
/export/Medien ariel(fsid=0b9b44e8-db76-4e7a-bcae-09db15e684a3,rw,subtree_check,insecure,all_squash,anonuid=1002,anongid=1004) 192.168.230.0/24(fsid=f08f0bc9-d057-4a7e-bd0b-2717a2c5d790,rw,subtree_check,insecure,all_squash,anonuid=1000,anongid=1004)
/export/Software 192.168.230.0/24(fsid=35cd7da8-d7f9-42fc-a748-a02ba22640d5,rw,subtree_check,insecure,all_squash,anonuid=1000,anongid=1005)
/export/Switch 192.168.230.0/24(fsid=ffce7637-e309-4eaa-9996-5bfadf04ea18,rw,subtree_check,insecure,all_squash,anonuid=1000,anongid=1006)

Alles anzeigen

See line #8 for the entry.

When I try to mount I got this:

Code

root@miranda:~# mount -t nfs -o nfsvers=3 uranus:export/Downloads /mnt/downloads/ -v
mount.nfs: timeout set for Wed Apr 17 10:40:32 2024
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: an incorrect mount option was specified

Alles anzeigen

I only enabled NFS v3 in OMV due to other problems, not related to this server.

I ran this config for a long time in OMV 6 without issues.

I don't know if the host itself (miranda) in OMV 6 shows up in the command showmount --exports uranus, maybe this was never the case. But it uses these host specific config when it gets mounted.

Can you help me to get NFS working again?

Peronia · 17. April 2024

Sorry, forget to mention: I already tried to delete all NFS shares and create it new, mentioned here. This has no effect.

ryecoaaron · 17. April 2024

Does this work? sudo mount -t nfs uranus:/export/Downloads /mnt/downloads/

Peronia · 17. April 2024

Usually my HDDs going into standby when no interaction happens for 10 minutes, so they were in standby. I try this command:

Code

root@miranda:~# mount -t nfs uranus:/export/Downloads /mnt/downloads/
mount.nfs: Connection refused

The HDD don't wake up (usually they should). I waked them manually and try it then again with the same result.

I executed mount -t nfs uranus:/export/Downloads /mnt/downloads/ -v and got this:

Code

root@miranda:~# mount -t nfs uranus:/export/Downloads /mnt/downloads/ -v
mount.nfs: timeout set for Wed Apr 17 13:25:23 2024
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: Connection refused

Alles anzeigen

ryecoaaron · 17. April 2024

I use nfs for everything on all of my OMV 7 servers without issue. What is the output of: sudo omv-salt deploy run nfs

Peronia · 17. April 2024

Yeah, nice if this were in my case equal. Here are the result:

Code

root@uranus:~# omv-salt deploy run nfs
debian:
----------
          ID: configure_nfs_conf
    Function: file.managed
        Name: /etc/nfs.conf.d/99-openmediavault.conf
      Result: True
     Comment: File /etc/nfs.conf.d/99-openmediavault.conf is in the correct state
     Started: 13:41:52.388232
    Duration: 111.966 ms
     Changes:
----------
          ID: configure_idmapd_conf
    Function: file.managed
        Name: /etc/idmapd.conf
      Result: True
     Comment: File /etc/idmapd.conf is in the correct state
     Started: 13:41:52.500327
    Duration: 99.089 ms
     Changes:
----------
          ID: divert_idmapd_conf
    Function: omv_dpkg.divert_add
        Name: /etc/idmapd.conf
      Result: True
     Comment: Leaving 'local diversion of /etc/idmapd.conf to /etc/idmapd.conf.distrib'
     Started: 13:41:52.599849
    Duration: 8.293 ms
     Changes:
----------
          ID: configure_nfs_exports
    Function: file.managed
        Name: /etc/exports
      Result: True
     Comment: File /etc/exports is in the correct state
     Started: 13:41:52.608293
    Duration: 169.792 ms
     Changes:
----------
          ID: divert_nfs_exports
    Function: omv_dpkg.divert_add
        Name: /etc/exports
      Result: True
     Comment: Leaving 'local diversion of /etc/exports to /etc/exports.distrib'
     Started: 13:41:52.778200
    Duration: 8.224 ms
     Changes:
----------
          ID: stop_nfs_blkmap_service
    Function: service.dead
        Name: nfs-blkmap
      Result: True
     Comment: The service nfs-blkmap is already dead
     Started: 13:41:53.524788
    Duration: 21.651 ms
     Changes:
----------
          ID: mask_nfs_blkmap_service
    Function: service.masked
        Name: nfs-blkmap
      Result: True
     Comment: Service nfs-blkmap is already masked
     Started: 13:41:53.546567
    Duration: 0.538 ms
     Changes:
----------
          ID: start_nfs_server_service
    Function: service.running
        Name: nfs-server
      Result: True
     Comment: The service nfs-server is already running
     Started: 13:41:53.547525
    Duration: 17.309 ms
     Changes:
----------
          ID: restart_nfs_utils_service
    Function: service.running
        Name: nfs-utils
      Result: True
     Comment: The service nfs-utils is already running
     Started: 13:41:53.565079
    Duration: 19.566 ms
     Changes:

Summary for debian
------------
Succeeded: 9
Failed:    0
------------
Total states run:     9
Total run time: 456.428 ms

Alles anzeigen

ryecoaaron · 17. April 2024

Have you tried mounting by ip address instead of hostname?

Peronia · 17. April 2024

Yes, same result

ryecoaaron · 17. April 2024

Ok, I figured it out. When you only have nfsv2 and/or nfsv3 enabled, OMV disabled nfs via tcp. I think this is wrong since nfs v3 does support tcp - https://github.com/openmediava…avault.conf.j2#L6C9-L6C68 votdev is there a reason you disabled tcp on nfs v3?

So, you can either mount with udp - sudo mount.nfs -o udp 192.168.1.125:/export/nfstest1 /mnt

or enable one or more of the nfs v4 protocols which will enable tcp in the nfs-kernel-server config.

Peronia · 17. April 2024

My problem with v4 was nautilus, which neither support v4 nor auto negation of the versions. So I keep stuck with v3.

When I try udp, I got this:

Code

root@miranda:~# mount -t nfs -o udp uranus:/export/Downloads /mnt/downloads/ -v
mount.nfs: timeout set for Wed Apr 17 14:50:43 2024
mount.nfs: trying text-based options 'udp,vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'udp,vers=4,minorversion=1,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'udp,vers=4,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'udp,addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 51985
mount.nfs: mount(2): Invalid argument
mount.nfs: an incorrect mount option was specified

Alles anzeigen

I also allowed v4 in OMV and got this:

Code

root@miranda:~# mount -t nfs uranus:/export/Downloads /mnt/downloads/ -v
mount.nfs: timeout set for Wed Apr 17 14:55:42 2024
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): No such file or directory
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 49642

Alles anzeigen

Strange that the connection takes place at v3 here.

Well, it got mounted with v3 UDP (not TCP)... I don't understand why v4 isn't used, maybe the path is not for v4? I have in mind that v4 don't need export I think.

Code

root@miranda:~# mount
...
uranus:/export/Downloads on /mnt/downloads type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.230.18,mountvers=3,mountport=49642,mountproto=udp,local_lock=none,addr=192.168.230.18)

ryecoaaron · 17. April 2024

Zitat von Peronia

I don't understand why v4 isn't used, maybe the path is not for v4? I have in mind that v4 don't need export I think.

If you want v4, mount it with just the share name: sudo mount.nfs 192.168.1.125:nfstest1 /mnt

Peronia · 17. April 2024

Okay, thanks. But UDP only works without the -o udp flag and if v4 is enabled via OMV. I think now I have the nautilus problem again

ryecoaaron · 17. April 2024

Disable nfs v4 in the omv web interface and apply changes.

Enable tcp in /etc/nfs.conf.d/99-openmediavault.conf

Restart nfs-kernel-server with sudo systemctl restart nfs-kernel-server

Does everything work then?

Peronia · 17. April 2024

Yes, works fine. The share got mounted with v3 and UDP:

Code

root@miranda:~# mount -t nfs uranus:/export/Downloads /mnt/downloads/ -v
mount.nfs: timeout set for Wed Apr 17 15:35:48 2024
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=192.168.230.18,clientaddr=192.168.230.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.230.18'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.230.18 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.230.18 prog 100005 vers 3 prot UDP port 45841
root@miranda:~# mount
...
uranus:/export/Downloads on /mnt/downloads type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.230.18,mountvers=3,mountport=45841,mountproto=udp,local_lock=none,addr=192.168.230.18)

Alles anzeigen

I don't understand why TCP don't work (I'm fine using UDP, think i had used it in OMV 6 too) and why UDP only works if I enable TCP.

ryecoaaron · 17. April 2024

Zitat von Peronia

why UDP only works if I enable TCP.

I can't replicate that problem.

Peronia · 17. April 2024

Zitat von ryecoaaron

I can't replicate that problem.

Do you mean you can't reproduce the problem itself or only the UDP thing?

ryecoaaron · 17. April 2024

Zitat von Peronia

Do you mean you can't reproduce the problem itself or only the UDP thing?

Just the part I quoted. I have no problem mounting via udp with udp enabled and tcp disabled.

Peronia · 22. April 2024

I'll keep it open since your solution is only a workaround. My change will get overwritten next time.

ryecoaaron · 22. April 2024

Zitat von Peronia

I'll keep it open since your solution is only a workaround. My change will get overwritten next time.

I would file an issue. https://github.com/openmediavault/openmediavault/issues

No NFS mount possible

Peronia 17. April 2024

Jetzt mitmachen!