Comment # 36 on bug 1048679 from Thomas Blume

(In reply to Franck Bui from comment #35)
> (In reply to Thomas Blume from comment #34)
> > Shouldn't we rather find out why ID_SERIAL gets overwritten by
> > ID_SERIAL_SHORT? I don't see any reason therefore in the initial upstream
> > request at: https://github.com/systemd/systemd/issues/1453
> > Why should nvme device treated differently from other block devices (e.g.
> > scsi or cciss)?
> 
> According to
> https://github.com/systemd/systemd/issues/1453#issuecomment-145231313, no
> SCSI is involved and the kernel is supposed to export the relevant bit in
> sysfs and systemd should use them.

Exporting the information via sysfs doesn't seem to be implemtend in the kernel
yet. 
But thanks for pointing this out, in this light, scsi_id is probably not the
right tool to extract the device information for nvme disks.
I've checked on an orthos machine and saw this:

cage:/sys/block/nvme0n1/:[127]# /lib/udev/scsi_id --export --whitelisted -d
/dev/nvme0n1 
ID_SCSI=1
ID_VENDOR=NVMe
ID_VENDOR_ENC=NVMe\x20\x20\x20\x20
ID_MODEL=Linux
ID_MODEL_ENC=Linux
ID_REVISION=73-5
ID_TYPE=disk
ID_SERIAL=SNVMe_Linux
ID_SERIAL_COMPAT=
ID_SERIAL_SHORT=
ID_SCSI_SERIAL=54893f3e68f807f6

So, neither ID_SERIAL or ID_SERIAL_SHORT seem to be the best to provide an
uniqe identifier. Questions is whether ID_SCSI_SERIAL is present on all nvme
devices.