http://bugzilla.suse.com/show_bug.cgi?id=1095096 http://bugzilla.suse.com/show_bug.cgi?id=1095096#c18 Franck Bui <fbui@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |jthumshirn@suse.com Flags|needinfo?(dariusz.ostolski@ |needinfo?(jthumshirn@suse.c |gmail.com) |om) --- Comment #18 from Franck Bui <fbui@suse.com> --- OK so I think the problem here is due to the replacement of the old compat rule dealing with nvme devices which used scsi_id. But since the scsi translation for nvme devices was depecrated in the kernel, we switched the code to use sysfs attributes only. @Johannes according to you this was a safe switch but apparently we obtain a different result here: - scsi_id returns the following serial id "200080d03000c85f8", see comment #17. - OTOH the new rule[1] using sysfs attributes returns something totally different: "SNVMe_THNSN5512GPUK NV17BB502BKSHU", see the value of "ID_NVME_SERIAL_COMPAT" returned by the output of "udevadm info" in comment #9. Can you see what's going wrong here ? [1] The new rule looks like this:

KERNEL=="nvme*", ENV{DEVTYPE}=="disk", ENV{ID_NVME_SERIAL_COMPAT}!="?*", ATTRS{model}=="?*", ATTRS{serial}=="?*", \ PROGRAM=="/bin/sh -c ' \ cd /sys/%p; \ while ! [ -f model ]; do \ cd ..; \ [ $(pwd) = %S ] && exit 1; \ done; \ cut -c 1-16 model'", ENV{ID_NVME_SERIAL_COMPAT}="SNVMe_%c%s{serial}"

KERNEL=="nvme*", ENV{DEVTYPE}=="disk", ENV{ID_NVME_SERIAL_COMPAT}=="?*", SYMLINK+="disk/by-id/nvme-$env{ID_NVME_SERIAL_COMPAT}"

-- You are receiving this mail because: You are on the CC list for the bug.