> As a more detailed comment, I think that looking at the device
> nodes is not the right level for LVM. Instead, we should look at the
> 'native' LVM objects, physical volumes, volume groups, pools, snapshots,
> and logical volumes. This means that pyblk needs to know about LVM, but
> if it doesn't, then it is much less useful for Cockpit, unfortunately.
This could be more or less complex. The current names shown are just
udev's DEVNAME and are not so informative, everybody agrees. Showing for
lvm the particularly names that dm uses would be absolutely straightforward.
But taking a plunge into showing whatever more complex relationships lvm
builds on top of dm would be another step. Currently, all operations rely
solely on information that can be extracted directly from sysfs or the
So the coding for this change really did take just five minutes
And the new results look something like this.
DEVNAME DMNAME DEVTYPE
/dev/nvme0n1 None disk None
`-/dev/md127 None disk None
|-/dev/dm-29 vg-cache0_cmeta disk None
`-/dev/dm-31 vg-lv_tdata disk None
`-/dev/dm-32 vg-lv-tpool disk None
|-/dev/dm-33 vg-lv disk None
`-/dev/dm-34 vg-thin1 disk None
Is that what you were getting at?
If you wanted to have the DMNAME override the DEVNAME whenever it was available that would
take another five minutes.
(I like to know where my data is coming from, so keeping them separate suits me).
> > _______________________________________________
> > cockpit-devel mailing list
> > cockpit-devel(a)lists.fedorahosted.org
> > https://email@example.com...
> - mulhern
> cockpit-devel mailing list