Hi, * Ville Korhonen [Thu Jan 10, 2019 at 06:45:40PM +0200]:
> Perhaps related to this, I've noticed horrific slowdowns with v2.03.02-1 > when running stuff inside chroot unless I bind-mount /run from the host > environment. Yesterday I noticed that it can take hours to run update-grub, > and I get tons of this same error message for each device/partition > WARNING: Device /dev/loop0 not initialized in udev database even after > waiting 10000000 microseconds. > Problem goes away immediately when I mount /run. Something related to > missing /run/udev. I can confirm this problem, it seems to have appeared with the upload of lvm 2.03.02-1. STR (with `/dev/mapper/$VG-$LV` corresponding to a LV): mkfs.ext4 /dev/mapper/$VG-$LV mount /dev/mapper/$VG-$LV /mnt debootstrap buster /mnt chroot /mnt apt -y install lvm2 mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev mount --bind /dev/pts /mnt/dev/pts chroot /mnt vgs Then the vgs process is horribly slow and causing many messages like: WARNING: Device /dev/... not initialized in udev database even after waiting 10000000 microseconds As soon as /run/udev is available inside the chroot, then lvm behaves as expected: mount --bind /run/udev /mnt/run/udev regards, -mika-
signature.asc
Description: Digital signature
