summaryrefslogtreecommitdiff
path: root/libdm
diff options
context:
space:
mode:
authorDavid Teigland <teigland@redhat.com>2022-08-31 16:05:07 -0500
committerDavid Teigland <teigland@redhat.com>2022-10-10 11:47:29 -0500
commit79e67fc5e4f28d19fe4d93e6831a3a60e9760b68 (patch)
tree618dc5d773e5d1dd129f2e2eb504aa6b67fa14dd /libdm
parent8de87e0207342b0142778ebe9c51f0d552adfab8 (diff)
downloadlvm2-79e67fc5e4f28d19fe4d93e6831a3a60e9760b68.tar.gz
device id: add new types using values from vpd_pg83
The new device_id types are: wwid_naa, wwid_eui, wwid_t10. The new types use the specific wwid type in their name. lvm currently gets the values for these types by reading the device's vpd_pg83 sysfs file (this could change in the future if better methods become available for reading the values.) If a device is added to the devices file using one of these types, prior versions of lvm will not recognize the types and will be unable to use the devices. When adding a new device, lvm continues to first use sys_wwid from the sysfs wwid file. If the device has no sysfs wwid file, lvm now attempts to use one of the new types from vpd_pg83. If a devices file entry with type sys_wwid does not match a given device's sysfs wwid file, the sys_wwid value will also be compared to that device's other wwids from its vpd_pg83 file. If the kernel changes the wwid type reported from the sysfs wwid file, e.g. from a device's t10 id to its naa id, then lvm should still be able to match it correctly using the vpd_pg83 data which will include both ids.
Diffstat (limited to 'libdm')
0 files changed, 0 insertions, 0 deletions