From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES storage 0/4] lvm plugin: error handling and locking fixes
Date: Mon,  3 Nov 2025 17:23:11 +0100	[thread overview]
Message-ID: <20251103162330.112603-1-f.ebner@proxmox.com> (raw)
Patch 1/4 is improving an error message by including the previously
captured error.
Patch 2/4 fixes error handling in volume_snapshot_rollback().
Previously, allocation would be ignored when 'saferemove' was enabled
on the storage.
Patches 3/4 and 4/4 fix the locking for volume import and snapshot
operations. Better viewed with "-w" or
"-w --word-diff=color --word-diff-regex='\w+'".
I noticed that the default timeout of 10 seconds for locking
essentially means only having 10 tries to acquire the lock [0], which
in a busy cluster might not be enough to get the lock with high
confidence. This is not fully orthogonal to the series here, since we
might want to either change that [0] or to use a higher timeout for
(some of) the callers here.
[0]: https://git.proxmox.com/?p=pve-cluster.git;a=blob;f=src/PVE/Cluster.pm;h=e829687a74224408106f74ee6873a44095f0ff4f;hb=HEAD#l601
pve-storage:
Fiona Ebner (4):
  lvm plugin: snapshot delete: propagate previously captured error
  lvm plugin: fix error handling in volume_snapshot_rollback()
  lvm plugin: volume import: lock allocation and removal sections
  lvm plugin: snapshot-as-volume-chain: use locking for snapshot
    operations
 src/PVE/Storage/LVMPlugin.pm | 128 ++++++++++++++++++++++++++---------
 1 file changed, 96 insertions(+), 32 deletions(-)
Summary over all repositories:
  1 files changed, 96 insertions(+), 32 deletions(-)
-- 
Generated by git-murpp 0.5.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next             reply	other threads:[~2025-11-03 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 16:23 Fiona Ebner [this message]
2025-11-03 16:23 ` [pve-devel] [PATCH storage 1/4] lvm plugin: snapshot delete: propagate previously captured error Fiona Ebner
2025-11-03 16:23 ` [pve-devel] [PATCH storage 2/4] lvm plugin: fix error handling in volume_snapshot_rollback() Fiona Ebner
2025-11-03 16:23 ` [pve-devel] [PATCH storage 3/4] lvm plugin: volume import: lock allocation and removal sections Fiona Ebner
2025-11-03 16:23 ` [pve-devel] [PATCH storage 4/4] lvm plugin: snapshot-as-volume-chain: use locking for snapshot operations Fiona Ebner
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=20251103162330.112603-1-f.ebner@proxmox.com \
    --to=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