In our case: Kernel: Linux version 4.18.0-513.18.1.el8_9.ppc64le (mockbu...@ppc-hv-13.build.eng.rdu2.redhat.com) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-20) (GCC)) #1 SMP Thu Feb 1 02:52:53 EST 2024 File systém type:xfs
-----Original Message----- From: Thomas Munro <thomas.mu...@gmail.com> Sent: Wednesday, September 11, 2024 12:45 PM To: Alvaro Herrera <alvhe...@alvh.no-ip.org> Cc: Pecsök Ján <jan.pec...@profinit.eu>; pgsql-general@lists.postgresql.org; Andres Freund <and...@anarazel.de> Subject: Re: Error:could not extend file " with FileFallocate(): No space left on device On Wed, Sep 11, 2024 at 9:56 PM Alvaro Herrera <alvhe...@alvh.no-ip.org> wrote: > On 2024-Sep-10, Pecsök Ján wrote: > > After upgrade of Posgres from version 13.5 to 16.2 we experience following > > error: > > could not extend file > > "pg_tblspc/16401/PG_16_202307071/17820/3968302971" with > > FileFallocate(): No space left on device > > > > We cannot easily replicate problem. It happens at randomly every 1-2 weeks > > of intensive query computation. > > Was there some changes in space allocation from Posgres 13.5 to Posgres > > 16.2? > > > > Database has size 91TB and has 27TB more space available. > > Yes, there were some changes in that area. I have a report from > somebody running EPAS 16 which has a problem that looks pretty much > the same as yours -- and the code is essentially identical. I gave > them the attached patch, hoping that it would shed some light ... but > so far, we've been unable to capture any useful intel. What kernel version and file system are these running on (both cases)?
