From: Kefu Chai <k.chai@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH v3 manager/storage 0/2] rbd: handle corrupt or inaccessible images gracefully
Date: Mon, 29 Jun 2026 19:48:25 +0800 [thread overview]
Message-ID: <20260629114827.2385004-1-k.chai@proxmox.com> (raw)
I tested this by deleting the header object of an RBD image. The
fallback triggered, the broken image appeared in 'pvesm list' with
size=-1, and a warning named it. Other images in the pool were
unaffected.
Changes since v2:
- Use traditional dereference (@$all_names) instead of postfix
dereference ($all_names->@*) for consistency with the rest of the file.
Kefu Chai (2):
fix #7000: rbd: handle corrupt or inaccessible images gracefully
storage: content: show inaccessible RBD images in UI
src/PVE/Storage/RBDPlugin.pm | 96 ++++++++++++++++++++++++++++++------
www/manager6/storage/ContentView.js | 3 +++
2 files changed, 85 insertions(+), 14 deletions(-)
--
2.47.3
next reply other threads:[~2026-06-29 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 11:48 Kefu Chai [this message]
2026-06-29 11:48 ` [PATCH v3 storage 1/2] fix #7000: rbd: handle corrupt or inaccessible images gracefully Kefu Chai
2026-06-29 11:48 ` [PATCH v3 manager 2/2] storage: content: show inaccessible RBD images in UI Kefu Chai
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=20260629114827.2385004-1-k.chai@proxmox.com \
--to=k.chai@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