Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #80982 > unrolled thread

Bug#1017720: nfs-common: No such file or directory

Started byVincent Lefevre <vincent@vinc17.net>
First post2023-11-29 16:30 +0100
Last post2025-02-18 01:30 +0100
Articles 5 — 1 participant

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1017720: nfs-common: No such file or directory Vincent Lefevre <vincent@vinc17.net> - 2023-11-29 16:30 +0100
    Bug#1017720: nfs-common: No such file or directory Vincent Lefevre <vincent@vinc17.net> - 2024-04-06 09:52 +0200
      Bug#1017720: nfs-common: No such file or directory Vincent Lefevre <vincent@vinc17.net> - 2024-04-09 14:20 +0200
        Bug#1017720: nfs-common: No such file or directory Vincent Lefevre <vincent@vinc17.net> - 2024-04-09 16:10 +0200
          Bug#1017720: nfs-common: No such file or directory Vincent Lefevre <vincent@vinc17.net> - 2025-02-18 01:30 +0100

#80982 — Bug#1017720: nfs-common: No such file or directory

FromVincent Lefevre <vincent@vinc17.net>
Date2023-11-29 16:30 +0100
SubjectBug#1017720: nfs-common: No such file or directory
Message-ID<HFuFH-9GP5-5@gated-at.bofh.it>
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 <vincent@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)

[toc] | [next] | [standalone]


#82178

FromVincent Lefevre <vincent@vinc17.net>
Date2024-04-06 09:52 +0200
Message-ID<Iq90l-4oGU-4359@gated-at.bofh.it>
In reply to#80982
On 2023-11-29 16:19:02 +0100, Vincent Lefevre wrote:
> 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.

And sometimes, the "stat" succeeds as expected, but the "open" that
follows gives a "No such file or directory" error.

Also note that in my case, the file under this filename is unique:
it is created only once (never deleted then recreated).

> The clients are Debian 11.8 machines (also nfs-common 1:1.3.4-6;
> 5.10.0-26-amd64 kernel).

Still the same problem with a Debian 12.5 machine (nfs-common 1:2.6.2-4;
6.1.0-18-amd64 (6.1.76-1) kernel) on the client side.

-- 
Vincent Lefèvre <vincent@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)

[toc] | [prev] | [next] | [standalone]


#82192

FromVincent Lefevre <vincent@vinc17.net>
Date2024-04-09 14:20 +0200
Message-ID<IriCd-57xm-1@gated-at.bofh.it>
In reply to#82178
On 2024-04-04 14:56:47 +0200, Vincent Lefevre wrote:
> On 2023-11-29 16:19:02 +0100, Vincent Lefevre wrote:
> > 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.
> 
> And sometimes, the "stat" succeeds as expected, but the "open" that
> follows gives a "No such file or directory" error.
> 
> Also note that in my case, the file under this filename is unique:
> it is created only once (never deleted then recreated).

Some additional information: created only once, but data may be
appended (on the creator's side, the file is created for writing,
and data are written occasionally, and at some point, the file is
closed). The error with "open" may occur even several hours after
the last time data were written to the file.

-- 
Vincent Lefèvre <vincent@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)

[toc] | [prev] | [next] | [standalone]


#82195

FromVincent Lefevre <vincent@vinc17.net>
Date2024-04-09 16:10 +0200
Message-ID<IrkkF-58EL-1@gated-at.bofh.it>
In reply to#82192

[Multipart message — attachments visible in raw view] — view raw

On 2024-04-09 14:09:43 +0200, Vincent Lefevre wrote:
> Some additional information: created only once, but data may be
> appended (on the creator's side, the file is created for writing,
> and data are written occasionally, and at some point, the file is
> closed). The error with "open" may occur even several hours after
> the last time data were written to the file.

This is actually reproducible with a read-only directory.
I've attached a Perl script to reproduce the issue, just
based on "stat".

The conditions seem to be:
  * The directory and the files need to be recent enough: I can't
    reproduce the issue with an old directory, even if I add many
    new files into it.
  * Concurrent "stat": with the attached script, the issue is
    reproducible with 2 threads or more, but not with a single
    thread.

Example of errors:

./dir-stat: can't stat . (x 2)
./dir-stat: can't stat 775 (x 148)
./dir-stat: can't stat 772 (x 1)
./dir-stat: can't stat 415 (x 1)
./dir-stat: can't stat 716 (x 1)
./dir-stat: can't stat 453 (x 1)
./dir-stat: can't stat 9 (x 1)
./dir-stat: can't stat 201 (x 1)
./dir-stat: can't stat 981 (x 1)
./dir-stat: can't stat 660 (x 1)
./dir-stat: can't stat 120 (x 1)
./dir-stat: can't stat 127 (x 1)
./dir-stat: can't stat 663 (x 1)

-- 
Vincent Lefèvre <vincent@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)

[toc] | [prev] | [next] | [standalone]


#85517

FromVincent Lefevre <vincent@vinc17.net>
Date2025-02-18 01:30 +0100
Message-ID<KhjES-6W-9@gated-at.bofh.it>
In reply to#82195
On 2024-04-09 15:58:21 +0200, Vincent Lefevre wrote:
> The conditions seem to be:
>   * The directory and the files need to be recent enough: I can't
>     reproduce the issue with an old directory, even if I add many
>     new files into it.
>   * Concurrent "stat": with the attached script, the issue is
>     reproducible with 2 threads or more, but not with a single
>     thread.

With a new script, it could be seen that the failures can occur
with various file systems, such as ext4 and tmpfs. So my problem
is not related to NFS. For those wondering, the bug I've just
reported:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098226

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web