Re: Fwd: Re: A new look at old NFS readdir() problems?

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: David Steele <david(at)pgbackrest(dot)org>
Cc: Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Larry Rosenman <ler(at)lerctr(dot)org>, Pgsql hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fwd: Re: A new look at old NFS readdir() problems?
Date: 2025-01-04 16:07:18
Message-ID: CA+hUKGJ9fedtbR-PT-83q4qK6X=b8UefjhhdVRbpHToQzpUvAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jan 4, 2025 at 5:48 AM David Steele <david(at)pgbackrest(dot)org> wrote:
> We had one issue reported [1] involving Alpine Linux and CIFS and

Not directly relevant for pgbackrest probably, but I noticed that
Alpine comes up in a few reports of failing rm -r on CIFS. I think it
might be because BSD and GNU rm use fts to buffer pathnames in user
space (narrow window), while Alpine uses busybox rm which has a
classic readdir()/unlink() loop:

https://github.com/brgl/busybox/blob/master/coreutils/rm.c
https://github.com/brgl/busybox/blob/master/libbb/remove_file.c

As for CIFS, there are lots of reports of this sort of thing from
Linux CIFS clients. I am suspicious of the 32 bit monotonic
resume_key apparently being used to seek to a starting position. I
don't plan to investigate myself, but ... is that even trying to avoid
skips and duplicates?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michel Pelletier 2025-01-04 16:37:39 Re: Using Expanded Objects other than Arrays from plpgsql
Previous Message Tom Lane 2025-01-04 08:15:51 Re: Fwd: Re: A new look at old NFS readdir() problems?