From: Joshua Huber via pve-devel <pve-devel@lists.proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Joshua Huber <jhuber@blockbridge.com>,
PVE Devel <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] missing udev properties in PVE9 beta
Date: Mon, 28 Jul 2025 10:43:24 -0400 [thread overview]
Message-ID: <mailman.184.1753713857.367.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <f4b8f451-c8eb-4e53-b59e-bed0ab46e911@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 6562 bytes --]
From: Joshua Huber <jhuber@blockbridge.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: PVE Devel <pve-devel@lists.proxmox.com>
Subject: Re: missing udev properties in PVE9 beta
Date: Mon, 28 Jul 2025 10:43:24 -0400
Message-ID: <CA+uqL0332oL5B9wBJX8EGLTJ4d-BaYjzuyiMdfSvM_tWJRk4VA@mail.gmail.com>
Hi Thomas,
Fantastic!
Thanks for creating a Debian bug & cherry-picked MR. Fingers crossed
the changes flow through into PVE9. :)
Take care,
Josh
On Sat, Jul 26, 2025 at 8:20 AM Thomas Lamprecht
<t.lamprecht@proxmox.com> wrote:
>
> Hi,
>
> On 26/07/2025 00:01, Joshua Huber wrote:
> > 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
>
> Thanks again for the heads up, as mentioned in the forum I also
> created a Debian bug report:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109923
>
> And created a merge request with a cherry-pick of this patch
> on the Debian package:
> https://salsa.debian.org/linux-blocks-team/sg3-utils/-/merge_requests/10
>
> > 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?
>
> Yeah, we will take a closer look and pick the fix up for our repos
> if nothing comes up.
>
> Thanks!
> Thomas
>
>
[-- 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 prev parent reply other threads:[~2025-07-28 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[not found] ` <CA+uqL0332oL5B9wBJX8EGLTJ4d-BaYjzuyiMdfSvM_tWJRk4VA@mail.gmail.com>
2025-07-29 11:58 ` Thomas Lamprecht
2025-07-30 10:07 ` Fabian Grünbichler
2025-07-25 22:01 Joshua Huber via pve-devel
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.184.1753713857.367.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=jhuber@blockbridge.com \
--cc=t.lamprecht@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