| From: | Michael Harris <harmic(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tomas Vondra <tomas(at)vondra(dot)me>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FileFallocate misbehaving on XFS |
| Date: | 2025-01-30 23:53:11 |
| Message-ID: | CADofcAVENSB2KEjWh2FW=RJOuWZmwQPbRJistj46Z-W6_4chxA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello All
An update on this.
Earlier in this thread, Jakub had suggested remounting the XFS
filesystems with the mount option allocsize=1m.
I've done that now, on a few systems that have been experiencing this
error multiple times a day, and it does seem to stop the errors from
occurring.
It has only been a few days, but it does look encouraging as a workaround.
From the xfs man page, it seems that manually setting allocsize turns
off the dynamic preallocation size heuristics that are normally used
by XFS.
The other piece of info is that we have raised a support ticket with
Redhat. I'm not directly in contact with them (it's another team that
handles that) but I will let you know of any developments.
Cheers
Mike
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2025-01-31 00:03:56 | Re: Skip collecting decoded changes of already-aborted transactions |
| Previous Message | Melanie Plageman | 2025-01-30 23:10:30 | Re: BitmapHeapScan streaming read user and prelim refactoring |