| From: | Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com> |
|---|---|
| To: | Michael Harris <harmic(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: FileFallocate misbehaving on XFS |
| Date: | 2024-12-09 10:27:40 |
| Message-ID: | CAKZiRmwa96qyGk6MbasLB-Qq6xMsZDy5yz+eyuOjGU9AViJS5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 9, 2024 at 10:19 AM Michael Harris <harmic(at)gmail(dot)com> wrote:
Hi Michael,
We found this thread describing similar issues:
>
>
> https://www.postgresql.org/message-id/flat/AS1PR05MB91059AC8B525910A5FCD6E699F9A2%40AS1PR05MB9105.eurprd05.prod.outlook.com
>
We've got some case in the past here in EDB, where an OS vendor has blamed
XFS AG fragmentation (too many AGs, and if one AG is not having enough
space -> error). Could You perhaps show us output of on that LUN:
1. xfs_info
2. run that script from https://www.suse.com/support/kb/doc/?id=000018219
for Your AG range
-J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2024-12-09 10:32:19 | Re: Conflict detection for update_deleted in logical replication |
| Previous Message | Alexander Kukushkin | 2024-12-09 10:27:06 | WARNING: missing lock on database "postgres" (OID 5) @ TID (0,4) |