Trying to create NFS share based on NFS mount

  • Hi,


    with help of the plugin Remote Mount I connected my external storage to my OMV by NFS.
    For one explicit folder I created a shared folder. This seems to work fine so far.


    Next I created a NFS share that points to the shared folder I created before.



    When I now try to mount the NFS share on my client, I get the following error:

    Code
    mount.nfs: access denied by server while mounting xxx.xxx.xxx.xxx:/export/xxx


    syslog on OMV server:


    Code
    Jan  7 19:07:31 openmediavault rpc.mountd[1517]: authenticated mount request from xxx.xxx.xxx.xxx:798 for /export/xxx (/export/xxx)
    Jan  7 19:07:31 openmediavault rpc.mountd[1517]: qword_eol: fflush failed: errno 22 (Invalid argument)
    Jan  7 19:07:31 openmediavault rpc.mountd[1517]: Cannot export /export/xxx, possibly unsupported filesystem or fsid= required


    fstab on client:


    Code
    xxx.xxx.xxx.xxx:/export/xxx  /mnt/storage  nfs  rsize=8192,wsize=8192,timeo=14,intr


    Isn't it possible to create a NFS share based on NFS mount?

    • Offizieller Beitrag

    There are probably a lot of permission issues with this setup. Why not just connect the client to the first NFS share instead of nfs to nfs?

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-2 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Well, my hope was to have a nice webinterface (OMV) in the middle, so that I'm flexible to create more shares with various services.
    Directly connect to the first NFS should be only the last option.

    • Offizieller Beitrag

    You might be able to use other services. Not sure. nfs can be very picky based on the settings you use. Are you mounting the nfs share on the first box with the insecure option?

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-2 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • first NFS:


    Code
    /mnt/xxx xxx.xxx.xxx.xxx(fsid=0,rw,no_root_squash,sync,no_subtree_check)

    But I already tried it with insecure on both server with the same result :(

    • Offizieller Beitrag

    I meant from the OMV box to the source not from the client to OMV.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-2 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Yes, I also tried it with both options (secure and insecure).



    Code
    root@openmediavault:/export# exportfs -a
    exportfs: /export/xxx does not support NFS export

    I think think I'll stick with direct conecting to the first NFS

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!