From: Joshua Huber via pve-devel <pve-devel@lists.proxmox.com>
To: PVE Devel <pve-devel@lists.proxmox.com>
Cc: Joshua Huber <jhuber@blockbridge.com>
Subject: [pve-devel] missing udev properties in PVE9 beta
Date: Fri, 25 Jul 2025 18:01:54 -0400 [thread overview]
Message-ID: <mailman.131.1753480968.367.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 5594 bytes --]
From: Joshua Huber <jhuber@blockbridge.com>
To: PVE Devel <pve-devel@lists.proxmox.com>
Subject: missing udev properties in PVE9 beta
Date: Fri, 25 Jul 2025 18:01:54 -0400
Message-ID: <CA+uqL03jnaXTaMvzqn-3q274bNhHEuiYQZf0QitdbeKetjG+Dg@mail.gmail.com>
Hi everyone,
While setting up automated testing for PVE9 we noticed that scsi block
devices were missing several udev properties.
After a bit of digging, the root cause turns out to be a regression in
the sg_inq tool (from sg3_utils). This bug slipped in as part of some
refactoring related to json output formatting on Feb 7, 2023.
I filed an issue upstream -- check it out for more details:
https://github.com/doug-gilbert/sg3_utils/issues/63
I also submitted a pull request which fixes the issue:
https://github.com/doug-gilbert/sg3_utils/pull/64
The likelihood of a new upstream release coming in time for the PVE9
release seems quite low. Perhaps a local patch for sg3_utils is in
order?
Take care,
Josh
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-07-25 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 22:01 Joshua Huber via pve-devel [this message]
[not found] <CA+uqL03jnaXTaMvzqn-3q274bNhHEuiYQZf0QitdbeKetjG+Dg@mail.gmail.com>
2025-07-26 12:20 ` Thomas Lamprecht
2025-07-28 14:43 ` Joshua Huber via pve-devel
[not found] ` <CA+uqL0332oL5B9wBJX8EGLTJ4d-BaYjzuyiMdfSvM_tWJRk4VA@mail.gmail.com>
2025-07-29 11:58 ` Thomas Lamprecht
2025-07-30 10:07 ` Fabian Grünbichler
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=mailman.131.1753480968.367.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=jhuber@blockbridge.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