lvs blocks a long time when /run is not mounted
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lvm2 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Installing into a chroot without /run mounted, grub's os-prober calls into lvs for details and it waits a very long time. I believe this is fixed upstream:
https:/
1. Eoan
2. lvm2 2.03.02-2ubuntu5
3. lvs doesn't hang
4. lvs waits up to 10 seconds for each device to be in udev
[ 181.186946] cloud-init[860]: Generating grub configuration file ...
[ 181.482159] cloud-init[860]: File descriptor 3 (pipe:[156394]) leaked on lvs invocation. Parent PID 336:
[ 191.524704] cloud-init[860]: WARNING: Device /dev/nvme0n1 not initialized in udev database even after waiting 10000000 microseconds.
[ 201.551563] cloud-init[860]: WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
[ 211.576785] cloud-init[860]: WARNING: Device /dev/md0 not initialized in udev database even after waiting 10000000 microseconds.
[ 221.604393] cloud-init[860]: WARNING: Device /dev/bcache0 not initialized in udev database even after waiting 10000000 microseconds.
[ 231.635862] cloud-init[860]: WARNING: Device /dev/bcache2 not initialized in udev database even after waiting 10000000 microseconds.
[ 241.662524] cloud-init[860]: WARNING: Device /dev/bcache4 not initialized in udev database even after waiting 10000000 microseconds.
[ 251.691894] cloud-init[860]: WARNING: Device /dev/vda not initialized in udev database even after waiting 10000000 microseconds.
[ 261.722293] cloud-init[860]: WARNING: Device /dev/nvme1n1 not initialized in udev database even after waiting 10000000 microseconds.
[ 271.755710] cloud-init[860]: WARNING: Device /dev/vda1 not initialized in udev database even after waiting 10000000 microseconds.
[ 281.790372] cloud-init[860]: WARNING: Device /dev/nvme0n1p1 not initialized in udev database even after waiting 10000000 microseconds.
[ 291.826365] cloud-init[860]: WARNING: Device /dev/nvme1n1p1 not initialized in udev database even after waiting 10000000 microseconds.
[ 301.861237] cloud-init[860]: WARNING: Device /dev/nvme0n1p2 not initialized in udev database even after waiting 10000000 microseconds.
[ 311.892953] cloud-init[860]: WARNING: Device /dev/nvme1n1p2 not initialized in udev database even after waiting 10000000 microseconds.
[ 321.924557] cloud-init[860]: WARNING: Device /dev/vdb not initialized in udev database even after waiting 10000000 microseconds.
[ 331.957529] cloud-init[860]: WARNING: Device /dev/vdc not initialized in udev database even after waiting 10000000 microseconds.
[ 341.990234] cloud-init[860]: WARNING: Device /dev/vdd not initialized in udev database even after waiting 10000000 microseconds.
[ 352.022321] cloud-init[860]: WARNING: Device /dev/vde not initialized in udev database even after waiting 10000000 microseconds.
[ 362.056566] cloud-init[860]: WARNING: Device /dev/vdf not initialized in udev database even after waiting 10000000 microseconds.
[ 372.091625] cloud-init[860]: WARNING: Device /dev/vdf1 not initialized in udev database even after waiting 10000000 microseconds.
[ 382.125340] cloud-init[860]: WARNING: Device /dev/vdf2 not initialized in udev database even after waiting 10000000 microseconds.
[ 392.159381] cloud-init[860]: WARNING: Device /dev/vdf3 not initialized in udev database even after waiting 10000000 microseconds.
[ 402.190582] cloud-init[860]: WARNING: Device /dev/vdg not initialized in udev database even after waiting 10000000 microseconds.
[ 412.219362] cloud-init[860]: WARNING: Device /dev/vdh not initialized in udev database even after waiting 10000000 microseconds.
[ 422.250694] cloud-init[860]: WARNING: Device /dev/vdh1 not initialized in udev database even after waiting 10000000 microseconds.
[ 432.281953] cloud-init[860]: WARNING: Device /dev/bcache1 not initialized in udev database even after waiting 10000000 microseconds.
[ 442.310473] cloud-init[860]: WARNING: Device /dev/bcache3 not initialized in udev database even after waiting 10000000 microseconds.
[ 452.336603] cloud-init[860]: WARNING: Device /dev/bcache5 not initialized in udev database even after waiting 10000000 microseconds.
[ 462.362582] cloud-init[860]: WARNING: Device /dev/vdi not initialized in udev database even after waiting 10000000 microseconds.
[ 472.395526] cloud-init[860]: WARNING: Device /dev/nvme0n1 not initialized in udev database even after waiting 10000000 microseconds.
[ 482.422127] cloud-init[860]: WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
[ 492.454553] cloud-init[860]: WARNING: Device /dev/md0 not initialized in udev database even after waiting 10000000 microseconds.
[ 502.484730] cloud-init[860]: WARNING: Device /dev/bcache0 not initialized in udev database even after waiting 10000000 microseconds.
[ 512.514417] cloud-init[860]: WARNING: Device /dev/bcache2 not initialized in udev database even after waiting 10000000 microseconds.
[ 522.545971] cloud-init[860]: WARNING: Device /dev/bcache4 not initialized in udev database even after waiting 10000000 microseconds.
[ 532.579838] cloud-init[860]: WARNING: Device /dev/nvme1n1 not initialized in udev database even after waiting 10000000 microseconds.
[ 542.610222] cloud-init[860]: WARNING: Device /dev/vda1 not initialized in udev database even after waiting 10000000 microseconds.
[ 552.640988] cloud-init[860]: WARNING: Device /dev/nvme0n1p1 not initialized in udev database even after waiting 10000000 microseconds.
[ 562.675101] cloud-init[860]: WARNING: Device /dev/nvme1n1p1 not initialized in udev database even after waiting 10000000 microseconds.
[ 572.709152] cloud-init[860]: WARNING: Device /dev/nvme0n1p2 not initialized in udev database even after waiting 10000000 microseconds.
[ 582.744043] cloud-init[860]: WARNING: Device /dev/nvme1n1p2 not initialized in udev database even after waiting 10000000 microseconds.
[ 592.780398] cloud-init[860]: WARNING: Device /dev/vdb not initialized in udev database even after waiting 10000000 microseconds.
[ 602.810999] cloud-init[860]: WARNING: Device /dev/vdc not initialized in udev database even after waiting 10000000 microseconds.
[ 612.843926] cloud-init[860]: WARNING: Device /dev/vdd not initialized in udev database even after waiting 10000000 microseconds.
[ 622.876291] cloud-init[860]: WARNING: Device /dev/vde not initialized in udev database even after waiting 10000000 microseconds.
[ 632.908315] cloud-init[860]: WARNING: Device /dev/vdf1 not initialized in udev database even after waiting 10000000 microseconds.
[ 642.938662] cloud-init[860]: WARNING: Device /dev/vdf2 not initialized in udev database even after waiting 10000000 microseconds.
[ 652.969504] cloud-init[860]: WARNING: Device /dev/vdg not initialized in udev database even after waiting 10000000 microseconds.
[ 663.001230] cloud-init[860]: WARNING: Device /dev/bcache1 not initialized in udev database even after waiting 10000000 microseconds.
[ 673.033116] cloud-init[860]: WARNING: Device /dev/bcache3 not initialized in udev database even after waiting 10000000 microseconds.
[ 683.063181] cloud-init[860]: WARNING: Device /dev/bcache5 not initialized in udev database even after waiting 10000000 microseconds.
[ 693.094720] cloud-init[860]: WARNING: Device /dev/vdi not initialized in udev database even after waiting 10000000 microseconds.
note, Disco lvm2 does not hang like this:
[ 173.322361] cloud-init[899]: Generating grub configuration file ...
[ 173.556604] cloud-init[899]: File descriptor 3 (pipe:[148718]) leaked on lvs invocation. Parent PID 300:
[ 173.564079] cloud-init[899]: WARNING: Failed to connect to lvmetad. Falling back to device scanning.
