From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mimecast-mx02.redhat.com (mimecast04.extmail.prod.ext.rdu2.redhat.com [10.11.55.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4D7F92026D25 for ; Tue, 24 Nov 2020 11:57:37 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D5BCF103B80A for ; Tue, 24 Nov 2020 11:57:37 +0000 (UTC) Received: by mail-il1-f170.google.com with SMTP id b8so3540225ila.13 for ; Tue, 24 Nov 2020 03:57:34 -0800 (PST) MIME-Version: 1.0 References: <20201120111433.GI1787072@localhost.localdomain> <20201123131321.GC2229389@localhost.localdomain> In-Reply-To: <20201123131321.GC2229389@localhost.localdomain> From: Sreyan Chakravarty Date: Tue, 24 Nov 2020 17:27:21 +0530 Message-ID: Content-Type: multipart/alternative; boundary="00000000000020df1605b4d904d6" Subject: Re: [linux-lvm] Unusually long boot times with LVM Snapshots Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: LVM general discussion and development --00000000000020df1605b4d904d6 Content-Type: text/plain; charset="UTF-8" On Mon, Nov 23, 2020 at 6:43 PM Bryn M. Reeves 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 --00000000000020df1605b4d904d6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Nov 23, 2020 at 6:43 PM Bryn = M. Reeves <bmr@redhat.com> wrot= e:
This is a cla= ssic (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 attribu= tes 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.

<= /div>
I have now migrated to thin snapshots:

T= hese are my logical volumes:

#=C2=A0 lvs

=C2=A0LV =C2=A0 =C2=A0 VG =C2=A0 =C2=A0 =C2=A0 Attr =C2=A0 = =C2=A0 =C2=A0 LSize =C2=A0 Pool =C2=A0 Origin Data% =C2=A0Meta% =C2=A0Move = Log Cpy%Sync Convert
=C2=A0 fedora vgfedora Vwi-a-tz-- 700.00g pool00 = =C2=A0 =C2=A0 =C2=A0 =C2=A016.61 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0
=C2=A0 pool00 vgfedora twi-aotz-- 929.75g =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 12.50 =C2=A016.61=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0


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 =C2=A0for LVM logical volumes = vgfedora/fedora
Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[88= 6]: inactive '/dev/vgfedora/pool00' [929.75 GiB] inherit
Nov 24 = 10:44:00 localhost.HPNotebook dracut-initqueue[886]: inactive '/dev/vgf= edora/fedora' [700.00 GiB] inherit
Nov 24 10:44:00 localhost.HPNoteb= ook dracut-initqueue[888]: modprobe: FATAL: Module dm-thin-pool not found i= n directory /lib/modules/5.8.18-200.fc32.x86_64
Nov 24 10:44:00 localhos= t.HPNotebook dracut-initqueue[888]: /usr/sbin/modprobe failed: 1
No= v 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 :

<= /div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 lvchange = -kn vgfedora/pool00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 lvchange -kn vgfedora/fedora

But no cha= nge.



How do I add th= e=20 dm-thin-pool module ? I can't even boot.

--=C2=A0
Regards,
Sreyan Chakravarty
--00000000000020df1605b4d904d6--