From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH-SERIES storage/qemu-server v3 00/11] fix #7094: external snapshot delete: ensure commit target is large enough
Date: Fri, 29 May 2026 21:49:59 +0200 [thread overview]
Message-ID: <178008419750.1121358.5044729878266348024.b4-ty@b4> (raw)
In-Reply-To: <20260519110646.25060-1-f.ebner@proxmox.com>
On Tue, 19 May 2026 13:06:25 +0200, Fiona Ebner wrote:
> Changes in v3:
> * rebase on latest master, need to bump APIAGE+VER one more
>
> Changes in v2:
> * rebase on latest master.
>
> For LVM storages using 'snapshot-as-volume-chain', it's necessary to
> ensure that the size for the LV of the target snapshot volume is large
> enough before doing a commit operation. This affects both the offline
> and the online case, which have different code paths.
>
> [...]
Applied, thanks!
[01/10] plugin: document volume_snapshot_info() method
commit: e48f10d2f64f374b035a88f8730adf32526941ca
[02/10] plugin: volume snapshot info: also return virtual size
commit: 1218bd79165273120adc9e60f80c94aedb2ea761
[03/10] plugin: document volume_resize() method
commit: 17545ce276a8feb060b850c160c8901cbe479990
[04/10] plugin/storage: volume resize: add snapname parameter
commit: b56c2d04e3d70d7d08e394bc56c65ba0772014c2
[05/10] lvm plugin: snapshot delete: clarify comment about using commit
commit: edcf4bfb322b21499e3007ea1cddfcd98537b3b8
[06/10] bump API age and version
commit: 2f7f7754425597c07a48869c592748c7b57f2db7
[07/10] partially fix #7094: lvm: snapshot delete: ensure commit target is large enough
commit: ee91a30f03ce810dd799a8a7577a352bf6ef316c
[08/10] plugin: volume snapshot info: don't set 'order' for internal snapshots
commit: 43d630f85864ef0fb2490f975c47cea50a88fd10
[09/10] plugin: volume snapshot info: correctly return internal snapshot information
commit: a7ff389fe2992eb95d7701cc046c3c05d1b91069
[10/10] plugin: volume snapshot info: do not set 'ext' property
commit: c0a77f74f790350562ab40cc0c13f344b55b9599
[qemu-server]
[1/1] partially fix #7094: external snapshot delete: ensure commit target is large enough
commit: 30e41d065623380cd4106f0524326c4da75b1cc9
prev parent reply other threads:[~2026-05-29 19:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 11:06 [PATCH-SERIES storage/qemu-server v3 00/11] fix #7094: external snapshot delete: ensure commit target is large enough Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 01/11] plugin: document volume_snapshot_info() method Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 02/11] plugin: volume snapshot info: also return virtual size Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 03/11] plugin: document volume_resize() method Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 04/11] plugin/storage: volume resize: add snapname parameter Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 05/11] lvm plugin: snapshot delete: clarify comment about using commit Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 06/11] bump API age and version Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 07/11] partially fix #7094: lvm: snapshot delete: ensure commit target is large enough Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 08/11] plugin: volume snapshot info: don't set 'order' for internal snapshots Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 09/11] plugin: volume snapshot info: correctly return internal snapshot information Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 10/11] plugin: volume snapshot info: do not set 'ext' property Fiona Ebner
2026-05-19 11:06 ` [PATCH qemu-server v3 11/11] partially fix #7094: external snapshot delete: ensure commit target is large enough Fiona Ebner
2026-05-26 13:57 ` [PATCH-SERIES storage/qemu-server v3 00/11] " Lukas Sichert
2026-05-26 14:08 ` Fiona Ebner
2026-05-26 14:36 ` Lukas Sichert
2026-05-29 19:49 ` Thomas Lamprecht [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=178008419750.1121358.5044729878266348024.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox