From: Nicolas Frey <n.frey@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH proxmox-backup v2 0/2] fix #7541: zfs status: account for msg directly after status in vdev parser
Date: Tue, 5 May 2026 16:16:04 +0200 [thread overview]
Message-ID: <20260505141606.438908-1-n.frey@proxmox.com> (raw)
As reported in Enterprise Support, when a spare is "INUSE", it has a
`msg` right after the STATUS, which the parser previously did not
account for.
Changes since v1:
* introduce new struct `VDevStats` to reduce boilerplate
proxmox-backup:
Nicolas Frey (2):
zfs: status: add `VDevStats` struct instead of 3 optional u64s
fix #7541: zfs status: account for msg directly after status in vdev
parser
src/tools/disks/zpool_status.rs | 51 +++++++++++++++++----------------
1 file changed, 26 insertions(+), 25 deletions(-)
Summary over all repositories:
1 files changed, 26 insertions(+), 25 deletions(-)
--
Generated by git-murpp 0.8.1
next reply other threads:[~2026-05-05 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 14:16 Nicolas Frey [this message]
2026-05-05 14:16 ` [PATCH proxmox-backup v2 1/2] zfs: status: add `VDevStats` struct instead of 3 optional u64s Nicolas Frey
2026-05-05 14:16 ` [PATCH proxmox-backup v2 2/2] fix #7541: zfs status: account for msg directly after status in vdev parser Nicolas Frey
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=20260505141606.438908-1-n.frey@proxmox.com \
--to=n.frey@proxmox.com \
--cc=pbs-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