On 2022-08-19 13:16:47 +0000, Jason Breitman wrote: > Package: nfs-common > Version: 1:1.3.4-6 > Severity: important > > Kernel: 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux > > -- Description > After updating and or creating new files on our file server via rsync, we > see many files report the error message below from NFSv4 clients since > upgrading from Debian 10.8 to Debian 11.4. > Clearing the dentry cache resolves the issue right away. > I am not sure that nfs-common is the package to blame, but listed it > based on the bug submission recommendations. > > -- Test > ls -l /mnt/dir/someOtherDir/* | grep '?' > > -- Error message > ls: cannot access 'filename': No such file or directory > -????????? ? ? ? ? ? filename
I have the same kind of issue at my lab with one of my programs: a readdir lists the file, but then a stat sometimes gives a "No such file or directory" error. Some clients are more affected that others. The clients are Debian 11.8 machines (also nfs-common 1:1.3.4-6; 5.10.0-26-amd64 kernel). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
