All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v3 0/5] ext4, xfs: discard the balloon on FITRIM
Date: Thu, 12 Nov 2026 13:08:45 +0100	[thread overview]
Message-ID: <179448532565.4060562.12568314333976356798.b4-ty@b4> (raw)
In-Reply-To: <20261111113135.4023555-1-den@openvz.org>

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
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-11-12 12:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 11:31 Denis V. Lunev
2026-11-11 11:31 ` [Devel] [PATCH hci-8.1 v3 1/5] ms/xfs: don't skip free extents in later batches of a whole-AG FITRIM Denis V. Lunev
2026-11-11 11:35   ` no-reply
2026-11-12 12:07   ` Konstantin Khorenko
2026-11-11 11:31 ` [Devel] [PATCH hci-8.1 v3 2/5] ms/xfs: don't skip free extents of the longest length in " Denis V. Lunev
2026-11-11 11:35   ` no-reply
2026-11-12 12:07   ` Konstantin Khorenko
2026-11-11 11:31 ` [Devel] [PATCH hci-8.1 v3 3/5] xfs: release the balloon inode when xfs_balloon_get() refuses it Denis V. Lunev
2026-11-11 11:35   ` no-reply
2026-11-12 12:07   ` Konstantin Khorenko
2026-11-11 11:31 ` [Devel] [PATCH hci-8.1 v3 4/5] ext4: discard the balloon on FITRIM Denis V. Lunev
2026-11-11 11:40   ` no-reply
2026-11-12 12:07   ` Konstantin Khorenko
2026-11-11 11:31 ` [Devel] [PATCH hci-8.1 v3 5/5] xfs: " Denis V. Lunev
2026-11-11 11:40   ` no-reply
2026-11-12 12:07   ` Konstantin Khorenko
2026-11-12 12:07 ` [Devel] [PATCH hci-8.1 v3 0/5] ext4, " Konstantin Khorenko
2026-11-12 12:08 ` Konstantin Khorenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=179448532565.4060562.12568314333976356798.b4-ty@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=devel@openvz.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.