Bug#925146: Acknowledgement (grub-probe appears to be stuck (in chroot))

[Colin Watson]

On Wed, Mar 20, 2019 at 02:13:22PM +0100, Harald Dunkel wrote:
> PS: strace reveals:
> 
> :
> access("/sys/devices/pci0000:00/0000:00:1d.2/0000:40:00.0/nvme/nvme0/nvme0n1/uevent", F_OK) = 0
> readlinkat(AT_FDCWD, "/sys/devices/pci0000:00/0000:00:1d.2/0000:40:00.0/nvme/nvme0/nvme0n1/subsystem", "../../../../../../../class/block", 4096) = 32
> openat(AT_FDCWD, "/sys/devices/pci0000:00/0000:00:1d.2/0000:40:00.0/nvme/nvme0/nvme0n1/uevent", O_RDONLY|O_CLOEXEC) = 3
> fstat(3, {st_mode=S_IFREG|0644, st_size=4096, ...}) = 0
> fstat(3, {st_mode=S_IFREG|0644, st_size=4096, ...}) = 0
> read(3, "MAJOR=259\nMINOR=0\nDEVNAME=nvme0n"..., 4096) = 47
> read(3, "", 4096)                       = 0
> close(3)                                = 0
> openat(AT_FDCWD, "/run/udev/data/b259:0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> :

This is not very informative: it's a tiny snapshot, and in any case
contains no timing data.

Would it be possible to get the full grub-probe.trace file resulting
from running this in the chroot?

  strace -f -tt -s 1024 -o grub-probe.trace /usr/sbin/grub-probe --device /dev/mapper/vg00-buster --target=fs_uuid

-- 
Colin Watson                                       [cjwatson at debian.org]