Re: FileFallocate misbehaving on XFS
От | Tomas Vondra |
---|---|
Тема | Re: FileFallocate misbehaving on XFS |
Дата | |
Msg-id | 499b7e28-3ad4-4088-9c9d-5bf0efde5127@vondra.me обсуждение исходный текст |
Ответ на | Re: FileFallocate misbehaving on XFS (Jakub Wartak <jakub.wartak@enterprisedb.com>) |
Ответы |
Re: FileFallocate misbehaving on XFS
|
Список | pgsql-hackers |
On 12/9/24 11:27, Jakub Wartak wrote: > On Mon, Dec 9, 2024 at 10:19 AM Michael Harris <harmic@gmail.com > <mailto:harmic@gmail.com>> wrote: > > Hi Michael, > > We found this thread describing similar issues: > > https://www.postgresql.org/message-id/flat/ > AS1PR05MB91059AC8B525910A5FCD6E699F9A2%40AS1PR05MB9105.eurprd05.prod.outlook.com <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 <https://www.suse.com/support/kb/doc/?id=000018219> for > Your AG range > But this can be reproduced on a brand new filesystem - I just tried creating a 1GB image, create XFS on it, mount it, and fallocate a 600MB file twice. Which that fails, and there can't be any real fragmentation. regards -- Tomas Vondra
В списке pgsql-hackers по дате отправления: