From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Unusually long boot times with LVM Snapshots
Date: Wed, 25 Nov 2020 12:36:11 +0000 [thread overview]
Message-ID: <20201125123611.GA2419337@localhost.localdomain> (raw)
In-Reply-To: <CAMaziXvoqVUOD=iAks4x9bhOxeZCNcGcT6mJwaJCUEk29AoTOw@mail.gmail.com>
On Tue, Nov 24, 2020 at 05:27:21PM +0530, Sreyan Chakravarty wrote:
> But I am unable to boot now due to these errors:
>
> Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[861]: Scanning
> devices dm-0 for LVM logical volumes vgfedora/fedora
> Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[886]: inactive
> '/dev/vgfedora/pool00' [929.75 GiB] inherit
> Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[886]: inactive
> '/dev/vgfedora/fedora' [700.00 GiB] inherit
> Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[888]: modprobe:
> FATAL: Module dm-thin-pool not found in directory
> /lib/modules/5.8.18-200.fc32.x86_64
> Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[888]:
> /usr/sbin/modprobe failed: 1
> Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[888]: Can't process
> LV vgfedora/fedora: thin target support missing from kernel?
>
> I have tried to mark the volumes as active by :
>
> lvchange -kn vgfedora/pool00
> lvchange -kn vgfedora/fedora
>
> But no change.
>
>
>
> How do I add the dm-thin-pool module ? I can't even boot.
Most likely you are just missing the dm-thin-pool module in the dracut
initramfs image.
You can re-build it with the following command:
# dracut -f /boot/initramfs-$(uname -r).img $(uname -r)
If the running kernel matches the initramfs you want to rebuild then
you can leave out the file and kernel version:
# dracut -f
To build an initramfs with only the drivers that the running host
uses add the -H switch (the dm-thin-pool module must be loaded at
the time you run dracut for this to work):
# dracut -fH
See the dracut man page for more details.
Regards,
Bryn.
next prev parent reply other threads:[~2020-11-25 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 14:16 [linux-lvm] Unusually long boot times with LVM Snapshots Sreyan Chakravarty
2020-11-20 11:14 ` Bryn M. Reeves
2020-11-20 16:18 ` Sreyan Chakravarty
2020-11-23 13:13 ` Bryn M. Reeves
2020-11-24 11:57 ` Sreyan Chakravarty
2020-11-25 8:45 ` Sreyan Chakravarty
2020-11-25 12:36 ` Bryn M. Reeves [this message]
2020-11-25 15:32 ` Sreyan Chakravarty
2020-11-21 8:21 ` Sreyan Chakravarty
2020-11-23 12:52 ` Bryn M. Reeves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201125123611.GA2419337@localhost.localdomain \
--to=bmr@redhat.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox