Fwd: Unusually long boot times with LVM Snapshots

[Sreyan Chakravarty <sreyan32@xxxxxxxxx>]

On Fri, Nov 20, 2020 at 12:38 PM Samuel Sieb <samuel@xxxxxxxx> wrote:

Edit /etc/lvm/lvm.conf, find the line in the "log {" section that has
"verbose = 0" and change it to "verbose = 1".  Then run "dracut -f".
Reboot and at the grub menu, edit the boot entry, remove the "quiet
rhgb" parameters from the linux command line, then boot it.  See what
it's doing doing that time.  After it's booted, you can also check
"dmesg" and possible the "journalct -b" for information.

I have set

      verbose = 1

and 

     level =7

the highest level, in the "log {" section of /etc/lvm/lvm.conf 

But I have seen no change in boot logs. Let me know if I am doing anything wrong.

I am checking the boot logs via :

            journalctl -b

Also no change in the dmesg output.

Nevertheless, the think I have found the problem:

Nov 20 21:14:15  dracut-initqueue[902]: Scanning devices dm-0  for LVM logical volumes vgfedora/fedora
Nov 20 21:14:16  dracut-initqueue[927]: inactive Original '/dev/vgfedora/fedora' [700.00 GiB] inherit
Nov 20 21:14:16  dracut-initqueue[927]: inactive Snapshot '/dev/vgfedora/pre_kde_Nov_9' [70.00 GiB] inherit
Nov 20 21:17:27  systemd[1]: Found device /dev/mapper/vgfedora-fedora.
Nov 20 21:17:27  systemd[1]: Found device /dev/disk/by-uuid/03aef3ba-dca1-4cba-a3f5-36c5c0fe948e.
Nov 20 21:17:27  systemd[1]: Reached target Initrd Root Device.

As you can see there is a 3 minute delay to load or find the snapshot.

The question is what do I do now ?

This is my entire boot log below:

https://pastebin.com/raw/275JPvZB

--

Regards,

Sreyan Chakravarty

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx