CentOS - Mar 2023 - EL9/udev generates wrong device nodes/symlinks with HPE Smart Array controller

Simon Matter <simon.matter at invoca.ch>
> 2) some symlinks created by udev are just wrong and therefore very
> dangerous to use:
> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0 -> ../../sda
> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part1 -> ../../sdb1
> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part2 -> ../../sdb2
   I think it maybe caused by sd driver asynchronous scanning.
   I am lucky that I didn't see this before. nvme may have similar
issues, but nvme has boot parameter to avoid it.
   Suse has boot parameter to avoid it.
   with EL9 we will wait until EL 9.3 if we are lucky.
   I had report issue: https://bugzilla.redhat.com/show_bug.cgi?id=2140017

Hi,
> Simon Matter <simon.matter at invoca.ch>
>> 2) some symlinks created by udev are just wrong and therefore very
>> dangerous to use:
>> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0 -> ../../sda
>> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part1 -> ../../sdb1
>> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part2 -> ../../sdb2
>
>    I think it maybe caused by sd driver asynchronous scanning.
>    I am lucky that I didn't see this before. nvme may have similar
> issues, but nvme has boot parameter to avoid it.
>    Suse has boot parameter to avoid it.
>    with EL9 we will wait until EL 9.3 if we are lucky.
>    I had report issue: https://bugzilla.redhat.com/show_bug.cgi?id=2140017
Thanks for confirming that I'm not alone with this "feature"

In the above example, it's much fun if you want to wipe the two partitions
on
/dev/disk/by-id/scsi-SHP_LOGICAL_VOLUME_500143801722C0B0 and therefore
wipe this device. You end up wiping the wrong disk!

When I see such things my blood start boiling :(

Regards,
Simon