SMB v3 mount reports 'Stale file handle' after mover is being run

[PavelK]

First, thank you for Unraid, I find it really useful. I have a question though: I am running server with 2 x 3 TB drives (one partity, one data). I also have 500MB SSD cache. The HW on which unraid runs is purely a NAS with exposed SMB user share, no docker/containers.

 

On one of my other machines - multimedia server - I have mounted the only user-share with SMB v3:

 

[root@silverbox nextcloud]# mount | grep cifs
//192.168.0.115/nextcloud-userdata on /var/lib/nextcloud/data type cifs (rw,relatime,vers=3.1.1,cache=strict,username=silverbox,uid=970,noforceuid,gid=970,noforcegid,addr=192.168.0.115,file_mode=0660,dir_mode=0770,hard,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1)

 

I have however noticed that

 

1. once there is a fresh file: [root@silverbox data]# echo hello > greeting.txt

2. press MOVE button (the button will be grayed out immediately, if the page is reloaded, than the bug does not occur! - I am however unable to say when you preform complete page reload and when you perform graying out the button)

3. once the mover has finished, the data directory fails to be listed with 'Stale file handle', but the systemctl thinks that everything is OK:

 

[root@silverbox nextcloud]# ls -al
ls: cannot access 'data': Stale file handle
total 12
drwxr-xr-x  4 nextcloud nextcloud 4096 Dec 16 21:52 .
drwxr-xr-x 21 root      root      4096 Dec 13 21:45 ..
drwxr-xr-x  5 nextcloud nextcloud 4096 Dec 16 21:55 apps
d?????????  ? ?         ?            ?            ? data
[root@silverbox nextcloud]# systemctl status var-lib-nextcloud-data.mount

● var-lib-nextcloud-data.mount - /var/lib/nextcloud/data
     Loaded: loaded (/etc/fstab; generated)
     Active: active (mounted) since Tue 2021-12-21 17:54:54 CET; 2min 2s ago
      Where: /var/lib/nextcloud/data
       What: //192.168.0.115/nextcloud-userdata
       Docs: man:fstab(5)
             man:systemd-fstab-generator(8)
      Tasks: 0 (limit: 19071)
     Memory: 12.0K
        CPU: 8ms
     CGroup: /system.slice/var-lib-nextcloud-data.mount

Dec 21 17:54:54 silverbox systemd[1]: Mounting /var/lib/nextcloud/data...
Dec 21 17:54:54 silverbox systemd[1]: Mounted /var/lib/nextcloud/data.
 

Note: When I do dmesg, there is a strange message (I do not know if it's related):

[71426.580822] CIFS: VFS: \\192.168.0.115\nextcloud-userdata Close unmatched open for MID:87951

 

Could you please help me with that issue? I have just found out, that the issue can be workarounded by using explicitly SMB version 2.1 with the mount command - I will follow this carefully if it's really a working workaround.