-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for diskio alias by UUID #2750
Comments
This issue is stale because it has been open for 3 months with no activity. |
I'd like to use Glances for some basic disk monitoring functionality, especially in terms of smart data. As is, Glances is promising but it was a sad moment when I realised disks are haphazardly identified only by instantiation order. If the device order changes then the previous stats don't match the current stats. In my example I currently have sda through sdk, no sdl (disk is dead), then sdm through sdq. Disk sdq was a replacement for sdl. On next reboot, sda through sdk might stay the same - but I can't really be certain until after the reboot. This means all old smart data doesn't match current data and that individual disks are not identified. I typically identify these by their id, label, or by UUID (as suggested in this issue). In shell for example:
The above three references are static and uniquely identify the same specific entities every time. For disk-specific things like smart, the serial number makes the most sense. For filesystems, the UUID makes the most sense. The label isn't as useful in this case - but it does uniquely identify the main OS installation filesystem mounted at It is also worth pointing out that LVM Logical Volumes and encrypted disks/partitions also show up in |
I've looked into what would be needed to help resolve this ; Nicolas already opened an issue for related work a while back: |
When declaring aliases for my disks, I realised its nonsense what I am doing, since dm-0, dm-1, dm-2, sda, sdb, sdc, sdd and so on can change with every boot, making my aliases invalid and pointing to inconsistent partitions / disks.
Is there a way, or maybe it needs to be implemented yet, that fixes this inconsistency problem by using uuid or something similar that should be constant like mapper names for alias settings?
Also I would be very interested in a custum order for disks and file sys. Currently it just orders by dm-0 to dm-N, respectivly sda1 to sdXY, but since this could potentially change with every boot it would be highly appreciated if its reorderable.
The text was updated successfully, but these errors were encountered: