linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Sreyan Chakravarty <sreyan32@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Unusually long boot times with LVM Snapshots
Date: Tue, 24 Nov 2020 17:27:21 +0530	[thread overview]
Message-ID: <CAMaziXvoqVUOD=iAks4x9bhOxeZCNcGcT6mJwaJCUEk29AoTOw@mail.gmail.com> (raw)
In-Reply-To: <20201123131321.GC2229389@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]

On Mon, Nov 23, 2020 at 6:43 PM Bryn M. Reeves <bmr@redhat.com> wrote:

> This is a classic (aka CoW/copy-on-write or "thick") snapshot since it
> was created with a size (-L 70GB). When creating a thin snapshot you do
> not specify a size for the snapshot LV - it consumes space from the
> associated thin pool as needed.
>
> Generally you can find information about the LVs on your system using
> the "lvs" command. The "Attr" field displays lv attributes including the
> volume type - see the NOTES section of 'man lvs' for the meaning of the
> values. The lvs report can also show you whether a snapshot is using CoW
> or thinp and the amount of data it is consuming.
>

I have now migrated to thin snapshots:

These are my logical volumes:

#  lvs

 LV     VG       Attr       LSize   Pool   Origin Data%  Meta%  Move Log
Cpy%Sync Convert
  fedora vgfedora Vwi-a-tz-- 700.00g pool00        16.61

  pool00 vgfedora twi-aotz-- 929.75g               12.50  16.61



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.

-- 
Regards,
Sreyan Chakravarty

[-- Attachment #2: Type: text/html, Size: 2955 bytes --]

  reply	other threads:[~2020-11-24 11:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 14:16 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 [this message]
2020-11-25  8:45         ` Sreyan Chakravarty
2020-11-25 12:36         ` Bryn M. Reeves
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='CAMaziXvoqVUOD=iAks4x9bhOxeZCNcGcT6mJwaJCUEk29AoTOw@mail.gmail.com' \
    --to=sreyan32@gmail.com \
    --cc=linux-lvm@redhat.com \
    --subject='Re: [linux-lvm] Unusually long boot times with LVM Snapshots' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).