NFS issue (stale file handle)

Hi,

I manage to create a NFS share with OMV and permissions seems OK.

I can mount it, create files (touch) and folders.

But, I got an issue with folder. The folder is created correctly but if I do, just after, a "ls dir", I get a "Stale file handle".

rudybzh@docker:/mnt$ sudo mount -t nfs 192.168.1.4:/NAS /mnt/temp/
rudybzh@docker:/mnt$ mkdir /mnt/temp/dir
rudybzh@docker:/mnt$ ll /mnt/temp | grep dir
drwxrwsr-x    2 rudybzh users    2 Mar 28 09:32 dir
rudybzh@docker:/mnt$ ll -n /mnt/temp | grep dir
drwxrwsr-x    2 1000 100    2 Mar 28 09:32 dir
rudybzh@docker:/mnt$ id
uid=1000(rudybzh) gid=1000(rudybzh) groups=1000(rudybzh),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),100(users),109(netdev)
rudybzh@docker:/mnt$ ll /mnt/temp/dir
ls: reading directory '/mnt/temp/dir': Stale file handle
total 0

On the server side, the NFS config is as follow :

# 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/NAS 192.168.1.8/32(fsid=xxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,rw,subtree_check,insecure,all_squash,anonuid=1000,anongid=100)

# NFSv4 - pseudo filesystem root
/export 192.168.1.8/32(ro,fsid=0,root_squash,no_subtree_check,hide)

Any ideas of what it could be please ?

It's 100% reproductible on my system... whatever directory I create, I got this error.

Thanks.

Hi, no ideas please ?

Zitat von Soma

Thema

Remotemount lost a NFS shared connection

First, posting this on Plugins, since NFS is running normal.

This is busting my head the last days and could use some pointers.
After doing the latest updates on both Pis (Server && Client), one of the 3 NFS shares I have in use, just disappeared from the clients:
Wireguarded Windows Explorer says that I don't have permission (always worked normal since I regedited to mount as the UID:GID of the owner of the files/folders.
And the other Pi on the same LAN with remotemount. (Keeps timing out)

On pi…

Soma

12. Februar 2023

See if this makes any sense.

Thanks for the share, I will have a look at these long explanations and try to understand because, to be honest, I a total newbie on NFS.

I’m just trying it for the 1st time due to issues I have with SMB. And this kind of errors just at the beginning are not really motivating.

Thanks for your advises.

Unfortunately, even after these steps :

- Unmount (no need to force)

- Disabling NFS service

- Removing share

- Apply on OMV

- Enabling NFS

- Creating share

The issue is exactly the same.

Well, after searches, readings, searches, readings, I think I found the reason here : https://github.com/nfs-ganesha/nfs-ganesha/issues/331

It's seems that I'm facing the exact same issue with the exact same desing :

Proxmox (ZFS pool) => 9p => VM (KVM) with OMV. And I'm trying to activate NFS on OMV on top of the 9p FS.

Looks like it's not possible, so I'll do another way.

Proxmox (ZFS pool) => bind mount => Container (LXC) => NFS sharing (without OMV I think...)

Hopefully, it will work this way.