Simon Matter
> 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
Hi,
> Simon Matter
>> 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
>
Simon Matter
> 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
Hi,
I see some strange and dangerous things happening on a HPE server with HPE
Smart Array controller where EL9 ends up with wrong device nodes/symlinks
to the attached disks/raid volumes:
(I didn't touch anything here but at 08:09 some symlinks were changed)
/dev/disk/by-id/:
lrwxrwxrwx 1 root
4 matches
Mail list logo