XAPI could store reference to block-device as by-(uu)id when presented an enumeration-dependant dev path

[ydirson]

When a user creates a SR using an enumeration-dependent dev path (eg. /dev/nvme2n1), this creates an opportunity for things to go wrong whenever enumeration order changes, which can be mitigated by using symlinks from /dev/disks/by-id/ or /dev/disks/by-uuid/ instead.

It seems be a good thing to add some protection against those enumeration-dependent dev path. There would be several options, like:

• just rejecting them (unless some "I know what I'm doing" flag is also given)
• looking up a more stable path and use it (unless some "I know what I'm doing" flag is also given)

Would there be any problems with such a change?