Bug 223259

Summary: support unique device ID's for HDD supervision
Product: [Unmaintained] ksysguard Reporter: TLingk
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: wishlist CC: TLingk
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description TLingk 2010-01-18 11:21:44 UTC
Version:           4.3.1 (using KDE 4.3.1)
OS:                Linux
Installed from:    openSUSE RPMs

I'm looking for a possibility to specify drives for monitoring using
their unique ID's instead of the "direct" device file (such as /dev/sda, /dev/sdb, etc.). Since devices are managed by udev, the device file assignment may change whenever a removable drive is plugged in/out. This messes up worksheets that have been created using a different drive configuration. Let's assume, for example, there are two hard disks installed in the system named "sda" and "sdb". Now a worksheet is created in KSysguard, that monitors these two drives. If I now shut down the computer, plug in an USB-drive and boot again, the device-file assignment may have changed (e.g. "sda" is now the usb-disk, "sdb" is the first hdd and "sdc" the second hard disk). If then the previously prepared worksheet is opened again, KSysguard does not monitor the drives, the worksheet has originally been created for.

Many Linux distributions provide a /dev/disk/by-id/ and a /dev/disk/by-path directory, that contain unique named links that automatically address the appropriate drive. Wouldn't it be possible to use these links, so the changing of device files wouldn't be an issue any more?

Furthermore, KSysguard does not list my raid volume, that is located in /dev/mapper.

Best regards
Comment 1 Becker Béla 2018-01-19 08:58:54 UTC
I would like to see this happen. The way my MB works, if I boot with a USB3.0 drive, it becomes /dev/sda, and my IO graphs become less useful.

I think that the best solution would be to list the devices as they appear in the /dev/disk/by-id directory. If there are many disks at least it is easy to identify them this way.
Comment 2 Christoph Cullmann 2024-09-23 21:01:13 UTC
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task.

If your wish is still valid for the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!