Closed ethaniel closed 2 years ago
The dirty hack that solved this for me was simply recreating the symlink as it was on the old machine. Since umockdev does all the heavy lifting, it was enough:
umockdev-run --device /mrz/umockdev.txt -- sh -c 'mkdir -p $UMOCKDEV_DIR/sys/dev/block ; ln -s ../../devices/pci0000:16/0000:16:01.0/0000:18:00.0/nvme/nvme0/nvme0n1 $UMOCKDEV_DIR/sys/dev/block/259:0 ; udevadm info --query=all --name=/dev/nvme0n1'
What's your umockdev version? It looks like one from before 0.15.2, as none of your recorded attributes are \n
terminated.
I can reproduce this on the current version, but for a different reason. There is some fallout from commit 1b58d24fb78e8297f2b0e96abb99fcbee7f37784. The recorded attribute now looks like this:
A: dev=7:23\n
and it creates a broken symlink:
'7:23'$'\n' -> ../../devices/virtual/block/loop23
Fixed in PR #158. It's still a little unclear to me how exactly it failed for you (as you seem to have an old umockdev version), but I tested it end to end with an NVME block device now.
Hello!
I'm doing:
umockdev-record /dev/nvme0n1 > umockdev.txt
on one host, and then transferumockdev.txt
to another host (which doesn't have /dev/nvme0).Then I run
umockdev-run --device umockdev.txt -- udevadm info --query=all --name=/dev/nvme0n1
and get thedevice node not found
error.Strace shows that udevadm is trying to find the
/tmp/umockdev.S1ZSD1/sys/dev/block/259:0
path which is missing:Am I missing something? I've attached my umockdev.txt file umockdev (3).txt