The new device_id identifier is meant to be unique even for devices with the same name. The primary user for this will be Anaconda which needs an ID that will be a unique string stable between reset() calls.
The device ID looks as follows:
name for disks, partitions and loop devices
LVM-<name> for LVM VGs and LVs
BTRFS-<uuid>-<name> for btrfs volumes and subvolumes
STRATIS-<name> for Stratis devices
LUKS-<name> for LUKS mapped devices
MDRAID-<name> for MD arrays
DM-<name> for generic DM devices
Btrfs is currently the only device type that allows duplicate names for volumes so UUID is used for btrfs volumes. For other devices (LVM, MD...) the device name must be unique so we can use the name with technology prefix.
The new
device_id
identifier is meant to be unique even for devices with the same name. The primary user for this will be Anaconda which needs an ID that will be a unique string stable betweenreset()
calls.The device ID looks as follows:
name
for disks, partitions and loop devicesLVM-<name>
for LVM VGs and LVsBTRFS-<uuid>-<name>
for btrfs volumes and subvolumesSTRATIS-<name>
for Stratis devicesLUKS-<name>
for LUKS mapped devicesMDRAID-<name>
for MD arraysDM-<name>
for generic DM devicesBtrfs is currently the only device type that allows duplicate names for volumes so UUID is used for btrfs volumes. For other devices (LVM, MD...) the device name must be unique so we can use the name with technology prefix.