From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Christian Ebner <c.ebner@proxmox.com>,
Hannes Duerr <h.duerr@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup v2] report: better hardware and system utilization overview.
Date: Thu, 6 Nov 2025 19:23:19 +0100 [thread overview]
Message-ID: <050bc302-f988-4ad4-9fe5-b86fa9a20d25@proxmox.com> (raw)
In-Reply-To: <9e527fda-e769-45e1-8299-1bc1c97978f2@proxmox.com>
Am 29.10.25 um 09:30 schrieb Christian Ebner:
> On 10/24/25 2:19 PM, Hannes Duerr wrote:
>> instead of `ls -l /dev/disk/by-id /dev/disk/by-path` the command
>> `bash -c ls -l /dev/disk/by-*` is beeing used which displays the discs not only
>> by-id and by-path, but also by-diskseq, by-label, by-uuid, and
>> by-partuuid, which can be very helpful when assigning iSCSI and
>> multipath devices.
>> The execution in bash allows the use of asterisks.
>>
>> `dmidecode -t bios` outputs the current BIOS version and which allows to
>> determine whether certain fixes have already been implemented in the
>> version or not.
>>
>> `lscpu` provides a good overview of the CPU being used, its flags, and
>> existing/non-existing mitigations.
>>
>> `lspci -nnk` displays all PCI devices and the drivers used, which is often
>> helpful when troubleshooting.
>>
>> `ip -details -statistics a` provides a detailed overview of the
>> available interfaces and statistics since the last boot. This
>> information is often helpful in addressing performance issues and
>> assessments.
>>
>> Suggested-by: Sviatoslav Brylenko <s.brylenko@proxmox.com>
>> Signed-off-by: Hannes Duerr <h.duerr@proxmox.com>
>> ---
>
> Patch looks good to me, although we probably should explicitly depend on
> `util-linux`, `dmidecode` and `pciutils` packages for `proxmox-backup-sever` in debian/control then to assure the expected binaries are installed.
>
Yes, that's especially important for those installing on top of Debian,
e.g. for inside a container or some other more minimal set up environment.
And the standard set that we add in the installer might also change.
And while a bit unlikely, it's not a given that these tools will always
be available after installing through our official ISO.
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-11-06 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 12:18 Hannes Duerr
2025-10-29 8:30 ` Christian Ebner
2025-11-06 18:23 ` Thomas Lamprecht [this message]
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=050bc302-f988-4ad4-9fe5-b86fa9a20d25@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=h.duerr@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