| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Kenneth Marshall <ktm(at)rice(dot)edu>, Larry Rosenman <ler(at)lerctr(dot)org>, Pgsql hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Strange issue with NFS mounted PGDATA on ugreen NAS |
| Date: | 2025-01-02 20:14:00 |
| Message-ID: | 298519.1735848840@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> I forgot to report back, but yesterday I spent time unsuccessfully
> trying to reproduce the problem with macOS client and NFS server
> using btrfs (a Synology NAS running some no-name version of Linux).
Also, I *can* reproduce it using the same NFS server and a FreeBSD
14.2 client. At least with this pair of machines, the behavior seems
deterministic: "createdb foo" followed by "dropdb foo" leaves the
same set of not-dropped files behind each time. I added a bit of
debug logging to rmtree.c and verified that it's not seeing anything
odd happening, except that readdir never returns anything about the
missed files.
I will file a bug report, unless you already did?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2025-01-02 20:26:28 | Fwd: Re: A new look at old NFS readdir() problems? |
| Previous Message | Sami Imseih | 2025-01-02 20:12:08 | Re: Vacuum statistics |