From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Joshua Huber <jhuber@blockbridge.com>
Cc: PVE Devel <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] missing udev properties in PVE9 beta
Date: Tue, 29 Jul 2025 13:58:13 +0200 [thread overview]
Message-ID: <0ee52e6e-7e36-47bc-9682-94738cd582a5@proxmox.com> (raw)
In-Reply-To: <CA+uqL0332oL5B9wBJX8EGLTJ4d-BaYjzuyiMdfSvM_tWJRk4VA@mail.gmail.com>
Hi Josh,
Am 28.07.25 um 16:43 schrieb Joshua Huber:
> Thanks for creating a Debian bug & cherry-picked MR. Fingers crossed
> the changes flow through into PVE9. :)
FYI: We just uploaded a build of sg3-utils with your patch included
into the pve-test trixie repo, it's version 1.48-2+pmx1.
I could easily reproduce the issue here and thus test the patch.
E.g., the output of `sq_inq --export` with the original version:
sg_inq --export /dev/sg5
SCSI_TPGS=0
SCSI_TYPE=medium changer
SCSI_VENDOR=QUANTUM
SCSI_VENDOR_ENC=QUANTUM\x20
And after upgrading to the newer version with your patch:
sg_inq --export /dev/sg5
SCSI_TPGS=0
SCSI_TYPE=medium changer
SCSI_VENDOR=QUANTUM
SCSI_VENDOR_ENC=QUANTUM\x20
SCSI_MODEL=UHDL
SCSI_MODEL_ENC=UHDL\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
SCSI_REVISION=0096
Thanks!
Thomas
_______________________________________________
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-29 11:57 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
[not found] ` <CA+uqL0332oL5B9wBJX8EGLTJ4d-BaYjzuyiMdfSvM_tWJRk4VA@mail.gmail.com>
2025-07-29 11:58 ` Thomas Lamprecht [this message]
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=0ee52e6e-7e36-47bc-9682-94738cd582a5@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=jhuber@blockbridge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.