On Wed, 11 Nov 2026 12:31:30 +0100, Denis V. Lunev wrote:
> ext4, xfs: discard the balloon on FITRIM
>
> The balloon holds filesystem space that never carries data, but its
> blocks are allocated, so FITRIM walks past them, and inflating the
> balloon is a plain fallocate() that does not discard either. Once the
> balloon is inflated over the blocks of removed files, e.g. on an online
> shrink of a Container disk, the ploop or qcow2 image keeps those
> clusters mapped for good, and compaction, which is FITRIM, does not
> give them back (VSTOR-153590).
>
> [...]
Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in
rh10-6.12.0-211.52.1.22.21.vz10, thanks!
[1/5] ms/xfs: don't skip free extents in later batches of a whole-AG FITRIM
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/2cd1118f9a7f
[2/5] ms/xfs: don't skip free extents of the longest length in a whole-AG FITRIM
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/54b149136857
[3/5] xfs: release the balloon inode when xfs_balloon_get() refuses it
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/af1a0755a838
[4/5] ext4: discard the balloon on FITRIM
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/39aa4cc013bd
[5/5] xfs: discard the balloon on FITRIM
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/eaadefa92505
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/devel
