On Fri, Jan 31, 2025 at 3:33 PM Jean-Christophe Arnu <jcarnu@gmail.com> wrote:
>
> Hello Mike,
>
> We encountered the same problem with a fixed allocsize=262144k. Removing this option seemed to fix the problem.We are
nowin an XFS managed allocation heuristic way. The problem does not show up since the change was made on monday, but
I'mnot totally sure it has fixed the problem.
> If we can provide you with more information, please let me know.
>
>
>
> Le ven. 31 janv. 2025 à 00:53, Michael Harris <harmic@gmail.com> a écrit :
>>
>> 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.
Hi Mike and Jean-Christophe ,
out of curiosity, did Redhat provide any further (deeper) information
on why too big preallocation (or what heuristics) on XFS can cause
such issues?
-J
