On Tue, Aug 27, 2024 at 06:12:43PM +0300, Fedor Pchelkin wrote: > The extent changeset may have some additional memory dynamically allocated > for ulist in result of clear_record_extent_bits() execution. This can happen, as clear_record_extent_bits adds more data to the changeset in some cases. What I don't see yet how it happens. An extent range must be split so that a new entry is added with different bits set. This is usual thing, but why does this happen with the quotas disabled.
