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

2019-03-20 Thread Colin Watson
On Wed, Mar 20, 2019 at 05:11:15PM +0100, Harald Dunkel wrote: > Attached you can find the output of > > strace -f -o /tmp/strace.log.txt -ttt -T vgs --options vg_uuid,pv_name > --noheadings --separator : > > run in the chroot. Apparently thats the part that gets extremely > slow. While I

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

2019-03-20 Thread Colin Watson
On Wed, Mar 20, 2019 at 02:13:22PM +0100, Harald Dunkel wrote: > PS: strace reveals: > > : > access("/sys/devices/pci:00/:00:1d.2/:40:00.0/nvme/nvme0/nvme0n1/uevent", > F_OK) = 0 > readlinkat(AT_FDCWD, >

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

2019-03-20 Thread Harald Dunkel
PPS: There is a lot of screen output of the upgrade session: : : Setting up mdadm (4.1-1) ... update-initramfs: deferring update (trigger activated) Generating grub configuration file ... File descriptor 3 (pipe:[145329]) leaked on vgs invocation. Parent PID 31909: /usr/sbin/grub-probe File

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

2019-03-20 Thread Harald Dunkel
PS: strace reveals: : access("/sys/devices/pci:00/:00:1d.2/:40:00.0/nvme/nvme0/nvme0n1/uevent", F_OK) = 0 readlinkat(AT_FDCWD, "/sys/devices/pci:00/:00:1d.2/:40:00.0/nvme/nvme0/nvme0n1/subsystem", "../../../../../../../class/block", 4096) = 32 openat(AT_FDCWD,