Re: FileFallocate misbehaving on XFS - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: FileFallocate misbehaving on XFS
Date
Msg-id a13585e6-9fcf-49b6-aa52-587664fb7d02@vondra.me
Whole thread Raw
In response to Re: FileFallocate misbehaving on XFS  (Andrea Gelmini <andrea.gelmini@gmail.com>)
List pgsql-hackers
On 12/9/24 10:47, Andrea Gelmini wrote:
> 
> 
> Il Lun 9 Dic 2024, 10:19 Michael Harris <harmic@gmail.com
> <mailto:harmic@gmail.com>> ha scritto:
> 
> 
>     Is this already being looked into?
> 
> 
> Funny, i guess it's the same reason I see randomly complain of WhatsApp
> web interface, on Chrome, since I switched to XFS. It says something
> like "no more space on disk" and logout, with more than 300GB available.
> 

If I understand the fallocate issue correctly, it essentially ignores
the offset, so "fallocate -o 0 -l LENGTH" fails if

    LENGTH + CURRENT_LENGTH > FREE_SPACE

But if you have 300GB available, that'd mean you have a file that's
close to that size already. But is that likely for WhatsApp?

> Anyway, just a stupid hint, I would try to write to XFS mailing list.
> There you can reach XFS maintainers of Red Hat and the usual historical
> developers, of course!!!
> 

Yes, I think that's a better place to report this. I don't think we're
doing anything particularly weird / wrong with fallocate().


regards

-- 
Tomas Vondra




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Memory leak in WAL sender with pgoutput (v10~)
Next
From: Alexander Kukushkin
Date:
Subject: WARNING: missing lock on database "postgres" (OID 5) @ TID (0,4)