Bug in NFS4?

daschmidt1994 · Aug 14th 2024

I have a share /tank/share/backups/proxmox named "proxmox".

Now I tried to mount it from a client with v4.

In the documentation:

Mount as NFSv3 the folder /export/Videos in /mnt/nfs:
Code
```
$ mount 172.34.3.12:/export/Videos /mnt/nfs
```

The output from the client mount | grep nfs:

Code

192.168.178.199:/proxmox on /mnt/pve/openmediavault type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.178.188,local_lock=none,addr=192.168.178.199)

But on my openmediavault server the data where stored in the root system under /export/proxmox and not on /tank/share/backups/proxmox

ryecoaaron · Aug 14th 2024

/export/proxmox is a bind mount to /tank/share/backups/proxmox. You should be able to see that in /etc/fstab.

daschmidt1994 · Aug 14th 2024

where is then the mistake?

I use my proxmox to backup on the nfs share, first I tried nfs3 and then nfs4.

With the nfs4 the proxmox only show about 200gb of disc space(I think root?!)

The /tank/share/backups/proxmox folder there are 12TB available

Display Spoiler

ryecoaaron · Aug 14th 2024

Quote from daschmidt1994

where is then the mistake?

I don't see any mistakes. OMV bind mounts the shared folders to create nfs shares. /export/proxmox is the nfs v3 path and /proxmox is nfs v4 path. Proxmox is using the v4 path correctly it seems from your output. I don't know why proxmox is reporting different free space values.

Krisbee · Aug 14th 2024

daschmidt1994 Is that 200GB used or 200GB avail? I can assure you there's no bug. If it works as expected on a linux desktop, why not on proxmox. For example:

On Desktop, NFS share:

Note Free Space value.

On OMV server:

Code

root@omvt:~# 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/odata 192.168.0.0/24(fsid=41c96625-f5f3-487a-a691-9ddc4040922d,rw,subtree_check,insecure,no_root_squash,crossmnt)
/export 192.168.0.0/24(ro,fsid=0,root_squash,no_subtree_check)
root@omvt:~# zfs list
NAME          USED  AVAIL  REFER  MOUNTPOINT
Opool        2.76G  16.1G    96K  /srv/Opool
Opool/odata  2.76G  16.1G  2.76G  /srv/Opool/odata

Display More

daschmidt1994 · Aug 14th 2024

Quote from ryecoaaron

I don't see any mistakes. OMV bind mounts the shared folders to create nfs shares. /export/proxmox is the nfs v3 path and /proxmox is nfs v4 path. Proxmox is using the v4 path correctly it seems from your output. I don't know why proxmox is reporting different free space values.

in /tank/share/backups/proxmox are 2 folders and in /exports/proxmox is only 1 folder

Display Spoiler

ryecoaaron · Aug 14th 2024

Is the images directory a symlink or mount to another filesystem? ls -al in your previous windows would be much more helpful.

daschmidt1994 · Aug 14th 2024

Quote from ryecoaaron

Is the images directory a symlink or mount to another filesystem? ls -al in your previous windows would be much more helpful.

in what windows you mean?

ryecoaaron · Aug 14th 2024

Quote from daschmidt1994

in what windows you mean?

In the windows where you only used ls to list what was in the bind mount and regular directory.

daschmidt1994 · Aug 14th 2024

Quote from ryecoaaron

In the windows where you only used ls to list what was in the bind mount and regular directory.

Code

root@openmediavault:/tank/share/backups/proxmox# ls -all
insgesamt 114
drwxrwsrwx 4 root       users  4 26. Jul 08:05 .
drwxrwsrwx 8 root       users  8 27. Jul 21:03 ..
drwxrwsr-x 2 backupuser users 72 14. Aug 12:04 dump
drwxr-sr-x 2 nobody     users  2 26. Jul 08:05 images

Code

root@openmediavault:/export/proxmox# ls -all
insgesamt 12
drwxr-xr-x 3 root root 4096 14. Aug 14:49 .
drwxr-xr-x 7 root root 4096 14. Aug 11:47 ..
drwxr-xr-x 2 root root 4096 14. Aug 14:49 dump

ryecoaaron · Aug 14th 2024

Have you tried rebooting?

daschmidt1994 · Aug 14th 2024

yes nothing changed

ryecoaaron · Aug 14th 2024

What is the output of:

grep proxmox /proc/mounts

sudo umount /export/proxmox

sudo mount -a

ls -al /export/proxmox

daschmidt1994 · Aug 14th 2024

now I delete the shared folder and tried it from zero now there is the problem I think.

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; setfacl --modify group:users:--x '/tank/share/backups' 2>&1' with exit code '1': setfacl: /tank/share/backups: Operation not supported

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; setfacl --modify group:users:--x '/tank/share/backups' 2>&1' with exit code '1': setfacl: /tank/share/backups: Operation not supported in /usr/share/php/openmediavault/system/process.inc:247
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/sharemgmt.inc(452): OMV\System\Process->execute()
#1 [internal function]: Engined\Rpc\ShareMgmt->set()
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(122): call_user_func_array()
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
#4 /usr/sbin/omv-engined(544): OMV\Rpc\Rpc::call()
#5 {main}

if i ignore the error it works 1 and I see the correct data and available size but after reboot it's back on the root directory

daschmidt1994 · Aug 16th 2024

ryecoaaron have you an idea what i'm doing wrong?

ryecoaaron · Aug 16th 2024

Not really. Seems like things are mounting out of order but I don't use zfs. So, not the best one to figure that out.

Krisbee · Aug 16th 2024

daschmidt1994 If the outputs shown in #10 above are meant as evidence of the problem you raise in #6, then as the creation date and other details do not match you're not comparing the directory contents at the same point in time.

You should not be seeing the "setfacl" errors as shown in #14 above if your pool and/or filesystem datasets properties were correctly set. Did you create your zpool via the zfs plugin, or was it imported into OMV? Ensure acltype=posix and xattr=sa.

The info you've posted does not clearly distinguish between zfs filesystem datasets and ordinary directories. Here's my example.

OMV:

Code

root@omvt:/# zfs list
NAME          USED  AVAIL  REFER  MOUNTPOINT
Opool        4.12G  14.8G    96K  /srv/Opool
Opool/odata  4.12G  14.8G  4.12G  /srv/Opool/odata
Opool/pdata   104K  14.8G   104K  /srv/Opool/pdata
root@omvt:/# ls -ld /srv/Opool/pdata/backups/proxmox
drwxrwsr-x 4 root users 4 Aug 16 16:32 /srv/Opool/pdata/backups/proxmox
root@omvt:/# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/vda1 during installation
UUID=bbeaebe2-46ca-47aa-9c8e-e22d5b84eb4b /               ext4    errors=remount-ro 0       1
# swap was on /dev/vda5 during installation
UUID=135d3dc1-ed30-4cd5-9c83-b76372ad418e none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
# >>> [openmediavault]
/srv/Opool/odata/               /export/odata   none    bind,nofail,_netdev     0 0
/srv/Opool/pdata/backups/proxmox/               /export/proxmox none    bind,nofail,_netdev     0 0
# <<< [openmediavault]
root@omvt:/# 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/odata 192.168.0.0/24(fsid=41c96625-f5f3-487a-a691-9ddc4040922d,rw,subtree_check,insecure,no_root_squash,crossmnt)
/export/proxmox 192.168.0.0/24(fsid=1e4974de-7b14-4510-b68d-78b28c407459,rw,subtree_check,insecure,no_root_squash,crossmnt)
/export 192.168.0.0/24(ro,fsid=0,root_squash,no_subtree_check)
root@omvt:/#

Display More

Proxmox:

OMV

Code

root@omvt:/# ls -lR /srv/Opool/pdata/backups/proxmox
/srv/Opool/pdata/backups/proxmox:
total 1
drwxr-sr-x 2 root users 2 Aug 16 16:30 dump
drwxr-sr-x 2 root users 2 Aug 16 16:30 images

/srv/Opool/pdata/backups/proxmox/dump:
total 0

/srv/Opool/pdata/backups/proxmox/images:
total 0
root@omvt:/#

Display More

daschmidt1994 · Aug 16th 2024

I think I created it per cli

Quote from Krisbee

Ensure acltype=posix and xattr=sa

acltype is off and xattr is on.

Can i change this without problems?

Krisbee · Aug 17th 2024

Yes.

daschmidt1994 · Aug 18th 2024

Krisbee now I have changed the settings in the zfs, now there are no errors when I create a shared folder.

Here is all that I have configured:

Code

root@openmediavault:/export/proxmox/dump# zfs list
NAME          USED  AVAIL  REFER  MOUNTPOINT
nvme          886K   450G    24K  /nvme
nvme/docker    31K   450G    31K  /nvme/docker
tank         1.81T  12.6T   336K  /tank
tank/share   1.81T  12.6T  1.81T  /tank/share


root@openmediavault:/export/proxmox/dump# ls -ld /tank/share/backups/proxmox/
drwxrwsr-x 3 root users 3 18. Aug 20:10 /tank/share/backups/proxmox/


root@openmediavault:/export/proxmox/dump# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=1c198e69-d914-45a4-8d01-3cc490727943 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=CD9B-6FF0  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/sda3 during installation
UUID=a967c912-5b0a-40fe-a17e-85bb1c66507a none            swap    sw              0       0
# >>> [openmediavault]
/dev/disk/by-uuid/94273e04-9139-4023-acf7-2f5b3fd5b562          /srv/dev-disk-by-uuid-94273e04-9139-4023-acf7-2f5b3fd5b562      ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/tank/share/frigate/            /export/frigate none    bind,nofail,_netdev     0 0
/tank/share/scan/               /export/scan    none    bind,nofail,_netdev     0 0
/tank/share/backups/homeassistant/              /export/homeassistant   none    bind,nofail,_netdev     0 0
/tank/share/backups/proxmox/            /export/proxmox none    bind,nofail,_netdev     0 0
# <<< [openmediavault]
192.168.178.86:/home/share /mnt/debian nfs defaults 0 0

Display More

Bug in NFS4?

Participate now!

Similar Threads

Issues with Server-Side Copy using Manjaro Client and Dolphin File Explorer

Enable NFS4 share to multiple subnets