From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Michael Köppl" <m.koeppl@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH common/storage 0/3] fix #8286: do not hold inherited locks in volume cleanup workers
Date: Thu, 19 Nov 2026 15:14:12 +0100 [thread overview]
Message-ID: <DMZ90CUX4P8I.2HPXSD8KCE3D3@proxmox.com> (raw)
In-Reply-To: <20261105163637.1318072-1-m.koeppl@proxmox.com>
Superseded-by:
https://lore.proxmox.com/pve-devel/20261119141302.600137-1-m.koeppl@proxmox.com/
On Thu Nov 5, 2026 at 5:36 PM CET, Michael Köppl wrote:
> Destroying a VM through the API with a disk on an LVM storage with
> saferemove=1 leaves its VMID locked until the wipe of the disk is done.
> The imgdel worker is forked while the qmdestroy worker holds the
> config lock and inherits the locked file handle. The worker keeps the
> lock held after the qmdestroy worker exited. Re-creating a VM with the
> same VMID fails with a lock timeout in the meantime.
>
> This series tries to keep the fix targeted, since closing all inherited
[snip]
prev parent reply other threads:[~2026-11-19 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 16:36 [PATCH common/storage 0/3] fix #8286: do not hold inherited locks in volume cleanup workers Michael Köppl
2026-11-05 16:36 ` [PATCH common 1/3] tools: lock file: add helper to close inherited lock handles Michael Köppl
2026-11-05 16:36 ` [PATCH storage 2/3] fix #8286: vdisk free: do not hold inherited locks in cleanup worker Michael Köppl
2026-11-05 16:36 ` [PATCH storage 3/3] lvm plugin: do not hold inherited locks in cleanup workers Michael Köppl
2026-11-19 14:14 ` Michael Köppl [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=DMZ90CUX4P8I.2HPXSD8KCE3D3@proxmox.com \
--to=m.koeppl@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 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.