Re: [linux-lvm] System completely unstable after migrating to thin pools
On Tue, Dec 1, 2020 at 3:55 AM John Stoffel wrote: > > I suspect you're toast. What are you trying to accomplish here > though? Trying to stuff 10 pounds of data into a 5 pound bag? *grin* > > I don't know what you mean by that. Do you mean that thin pools cannot be migrated to from older LVMs ? > Or are you trying to have the ability to take snapshots of your system > to make rollbacks easier? > > Yes. > You need to post the output of your configuration in more detail, with > dmesg output, logs, lvs, pvs, vgs output, etc. > > $ lvs LV VG Attr LSizePool Origin Data% Meta% Move Log Cpy%Sync Convert fedora vgfedora Vwi-aotz-- 700.00g pool0016.66 pool00 vgfedora twi-aotz-- <929.76g 12.54 16.62 $ pvs PVVG Fmt Attr PSize PFree /dev/mapper/luks-2ec7f1ae-6f9b-4896-a7b2-be7809e9d2f4 vgfedora lvm2 a-- 929.99g 120.00m $ vgs VG #PV #LV #SN Attr VSize VFree vgfedora 1 2 0 wz--n- 929.99g 120.00m dmesg: https://pastebin.com/raw/svTX92SJ > But really, you do have backups? > > No. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] Search in the list
On Fri, Nov 27, 2020 at 9:48 AM Ilia Zykov wrote: > Hello. > Please, tell me if there is a way to search the archive of this list? > https://www.redhat.com/archives/linux-lvm/index.html > Thanks. > I don't think there is any way. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] swap on thin-provisioning
On Sun, 29 Nov 2020, 6:23 pm Gionatan Danti, wrote: > Il 2020-11-29 01:18 Chris Murphy ha scritto: > > What about a swapfile (on ext4 or XFS) onr a thin volume? In this > > case, I'd expect fallocate would set the LE to PE mapping, and it > > should work. But does it work for both paging and hibernation files? > > If things did not change, fallocate does *not* allocate PE space (ie: > they are not passed down to the underlying thin pool). > > Moreover, I expect for a memory-starved machine to page out pool > metadata (right?) so I would not use a thin volume for swap. > > Regards. > What about a swap file allocated with dd?? > > ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] Search in the list
On Fri, 27 Nov 2020, 9:52 pm Konstantin Ryabitsev, < konstan...@linuxfoundation.org> wrote: > On Fri, Nov 27, 2020 at 12:40:40PM +0300, Ilia Zykov wrote: > > Hello. > > Please, tell me if there is a way to search the archive of this list? > > https://www.redhat.com/archives/linux-lvm/index.html > > I realized that we don't have it on lore yet, so I imported mailman > archives and it should now be available here: > https://lore.kernel.org/linux-lvm/ > > Regards, > -K > > ___ > linux-lvm mailing list > linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ This mail list is already on mailman. I just checked. > > > ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
[linux-lvm] System completely unstable after migrating to thin pools
Hi, I have migrated to thin pools using partclone. But now that I am using thin pools my system is completely unstable. My swap is not activated : swapon[1004]: swapon: /fedora.swap: read swap header failed systemd[1]: fedora.swap.swap: Swap process exited, code=exited, status=255/EXCEPTION systemd[1]: fedora.swap.swap: Failed with result 'exit-code'. Failed to activate swap /fedora.swap. Dependency failed for Swap. swap.target: Job swap.target/start failed with result 'dependency'. My System logging service is not started: rsyslog.service: Failed with result 'core-dump'. Failed to start System Logging Service. SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rsyslog comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' rsyslog.service: Scheduled restart job, restart counter is at 1. And device mapper gives me weird messages during startup like: kernel: device-mapper: btree spine: node_check failed: csum 3318704195 != wanted 3318554075 kernel: device-mapper: block manager: btree_node validator check failed for block 220 kernel: device-mapper: btree spine: node_check failed: csum 3318704195 != wanted 3318554075 kernel: device-mapper: block manager: btree_node validator check failed for block 220 kernel: device-mapper: btree spine: node_check failed: csum 3318704195 != wanted 3318554075 kernel: device-mapper: block manager: btree_node validator check failed for block 220 kernel: device-mapper: btree spine: node_check failed: csum 3318704195 != wanted 3318554075 kernel: device-mapper: block manager: btree_node validator check failed for block 220 Also some dracut module is missing: dracut-initqueue[867]: /usr/sbin/thin_check: execvp failed: No such file or directory dracut-initqueue[867]: WARNING: Check is skipped, please install recommended missing binary /usr/sbin/thin_check! In short my system has gone to hell. This all started when I did a fstrim like this: sudo fstrim -v / And it returned an input/output error. My logical volumes were marked with two 'XX', I don't know what that means. After that I restarted. What can I do to get my system back to normal ? Please help. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
[linux-lvm] Is TRIM and DISCARD needed for normal HDD ?
Hi, I am using thin LVM pools, but I have a normal hard disk and not a SSD. Is there any reason to enable TRIM and/or DISCARD for my HDD ? I have heard it is only useful for a SSD. Will it offer any advantages in my case ? -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] Unusually long boot times with LVM Snapshots
On Wed, Nov 25, 2020 at 8:50 PM Bryn M. Reeves wrote: > 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. > Yes, I did do the above thanks. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] What is the use of thin snapshots if the external origin cannot be set to writable ?
On Tue, Nov 24, 2020 at 5:29 PM Sreyan Chakravarty wrote: > Do I have to reinstall my system for thin snapshots ? > > Can't I just clone my filesystem and then create a thin pool ? > >> > > Used partclone to restore my backup. Did not have re-install but did have to delete old volumes. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] System bricked after moving to thin snapshots
On Wed, Nov 25, 2020 at 8:50 PM Bryn M. Reeves wrote: > > See my reply to your other message - you need to rebuild your initramfs > image to include the dm-thin-pool module. > Yes I did that. Thanks. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] What is the use of thin snapshots if the external origin cannot be set to writable ?
On Wed, Nov 25, 2020 at 8:50 PM Bryn M. Reeves wrote: > You can, it's just typically easier for most users to re-install than to > execute the necessary steps to convert the system after the fact. > > If you have sufficient space then you can just create a thin pool, copy > your existing file systems into it and then fix up the fstab, grub boot > entries, initramfs and any other configuration that may still reference > the old device names. Once you're finished you can remove the original > volumes and reclaim the space for use by the thin pool. > Yes, I have migrated to thin pools successfully. Thanks. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] System bricked after moving to thin snapshots
Never mind. Had to regenerate my initramfs. On Tue, Nov 24, 2020 at 5:34 PM Sreyan Chakravarty wrote: > Hi, > > I have cloned my original root LVM, and then migrated to the newer thin > LVMs using partclone. > > Both backup and restore went off without causing any problems. > > But when I am now trying to boot into my system, it asks for the > encryption LUKS passphrase but after that I am getting: > > dracut-initqueue[300]: Warning: dracut-initqueue timeout - > starting timeout scripts > > This are my current logical volumes: > > # lvs > > LV VG Attr LSize Pool Origin Data% Meta% Move Log > Cpy%Sync Convert > fedora vgfedora Vwi-a-tz-- 700.00g pool0016.61 > > pool00 vgfedora twi-aotz-- 929.75g 12.50 16.61 > > > I keep getting the error: > > Scanning devices dm-0 for LVM logical volumes vgfedora/fedora > inactive '/dev/vgfedora/pool00' [929.75 GiB] inherit > inactive '/dev/vgfedora/fedora' [700.00 GiB] inherit > modprobe: FATAL: Module dm-thin-pool not found in directory > /lib/modules/5.8.18-200.fc32.x86_64 > /usr/sbin/modprobe failed: 1 > Can't process LV vgfedora/fedora: thin target support missing from kernel? > > I have marked the logical volumes as active via : > lvchange -kn vgfedora/pool00 > lvchange -kn vgfedora/fedora > > How can I add the dm-thin-pool module ? I can't even boot. > > Please let me know if any other info is required from my side. > > Need some help as I am unable to use my laptop. > > -- > Regards, > Sreyan Chakravarty > -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] Unusually long boot times with LVM Snapshots
On Tue, Nov 24, 2020 at 5:27 PM 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. > > Never mind, I have solved it by regenerating my initramfs. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
[linux-lvm] System bricked after moving to thin snapshots
Hi, I have cloned my original root LVM, and then migrated to the newer thin LVMs using partclone. Both backup and restore went off without causing any problems. But when I am now trying to boot into my system, it asks for the encryption LUKS passphrase but after that I am getting: dracut-initqueue[300]: Warning: dracut-initqueue timeout - starting timeout scripts This are my current logical volumes: # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert fedora vgfedora Vwi-a-tz-- 700.00g pool0016.61 pool00 vgfedora twi-aotz-- 929.75g 12.50 16.61 I keep getting the error: Scanning devices dm-0 for LVM logical volumes vgfedora/fedora inactive '/dev/vgfedora/pool00' [929.75 GiB] inherit inactive '/dev/vgfedora/fedora' [700.00 GiB] inherit modprobe: FATAL: Module dm-thin-pool not found in directory /lib/modules/5.8.18-200.fc32.x86_64 /usr/sbin/modprobe failed: 1 Can't process LV vgfedora/fedora: thin target support missing from kernel? I have marked the logical volumes as active via : lvchange -kn vgfedora/pool00 lvchange -kn vgfedora/fedora How can I add the dm-thin-pool module ? I can't even boot. Please let me know if any other info is required from my side. Need some help as I am unable to use my laptop. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] What is the use of thin snapshots if the external origin cannot be set to writable ?
On Mon, Nov 23, 2020 at 6:34 PM Bryn M. Reeves wrote: > OK - I understand what's going on in your environment now, thanks! > > Unfortunately it's not possible to have a writable external origin when > using device-mapper thin provisioned snapshots. To be able to write to > the origin while snapshots exist the origin device must also be a thin > provisioned logical volume. > > This is explained in more detail in the kernel documentation for the > thin provisioning targets. > > Documentation/admin-guide/device-mapper/thin-provisioning.rst: > > External snapshots > -- > > You can use an external **read only** device as an origin for a > thinly-provisioned volume. Any read to an unprovisioned area of the > thin device will be passed through to the origin. Writes trigger > the allocation of new blocks as usual. > > One use case for this is VM hosts that want to run guests on > thinly-provisioned volumes but have the base image on another device > (possibly shared between many VMs). > > You must not write to the origin device if you use this technique! > Of course, you may write to the thin device and take internal snapshots > of the thin volume. > > This allows a few niche use cases (like the VM example given), but it's > not the conventional way of using snapshots with thinp and it does > restrict what you can do. > > This means that to use thinp snapshots most effectively you must set the > system up with a thin pool from the start (e.g. using the distro's > installer to set up the VG). > > > Command on LV vgfedora/fedora uses options that are invalid > > with LV parameters: lv_is_external_origin. > > This is correct: currently you cannot make the origin writable since it > is an external snapshot. > > There is some work going on at the moment that would make device-mapper > type features more flexible and available in other device types, but > with the features provided by current tools and the thinp kernel > support you need to use a thinp device for the snapshot origin too. > > > Is there some sort of resolution ? > > It means re-installing but if the system is set up to use a thin pool > and thin provisioned logical volumes from the start then you can use > snapshots without any of the limitations that you've bumped into with > external origin devices. Do I have to reinstall my system for thin snapshots ? Can't I just clone my filesystem and then create a thin pool ? > > -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] Unusually long boot times with LVM Snapshots
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 pool0016.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 ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
[linux-lvm] What is the use of thin snapshots if the external origin cannot be set to writable ?
I am looking into thin snapshots since the older COW snapshots delay my boot enormously. My normal root fs is on a normal "non-thin" volume. So to make a snapshot I have boot into a live cd environment then set my root fs volume to read-only and then set it to inactive. Commands: sudo lvchange -pr vgfedora/fedora sudo lvchange -an vgfedora/fedora Now I create the thin snapshot using lvcreate, after that I need to restore my root LVS to its original state: sudo lvchange -ay vgfedora/fedora sudo lvchange -prw vgfedora/fedora This fails with: Command on LV vgfedora/fedora uses options that are invalid with LV parameters: lv_is_external_origin. I mean what is the point of creating a snapshot if I can't change my original volume ? Is there some sort of resolution ? -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] Unusually long boot times with LVM Snapshots
On Fri, Nov 20, 2020 at 4:45 PM Bryn M. Reeves wrote: > What type of snapshot are you using? LVM2 allows either "classic" CoW > snaps, > or the newer thin provisioned snapshots using the dm-thinp target. > > Classic snapshots are known to have very poor IO performance when multiple > snapshots of the same volume exist simultaneously (especially for write- > heavy workloads). > > Thin provisioned snapshots are not normally activated at boot time unless > they are explicitly requested (via dracut's rd.lvm.lv options) since they > have the skip activation flag set by default. > I tried thin snapshots, but what use are they if I can't use my system all together. Once my root logical volume was marked read only I could not revert it back to writable, after the snapshot was created. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Re: [linux-lvm] Unusually long boot times with LVM Snapshots
On Fri, Nov 20, 2020 at 4:45 PM Bryn M. Reeves wrote: > What type of snapshot are you using? LVM2 allows either "classic" CoW > snaps, > or the newer thin provisioned snapshots using the dm-thinp target. > > Classic snapshots are known to have very poor IO performance when multiple > snapshots of the same volume exist simultaneously (especially for write- > heavy workloads). > > Thin provisioned snapshots are not normally activated at boot time unless > they are explicitly requested (via dracut's rd.lvm.lv options) since they > have the skip activation flag set by default. > > How can I check which type of snapshot I am using ? I am very interested in knowing more about these newer snapshots. I think I am using the older COW snapshots. I created it using: sudo lvcreate -L 70GB -s -n test_snapshot /dev/mapper/vgfedora-fedora Is there any indication in the log of what's happening during the delay? > Look through the journalctl output to see if there are any messages logged > while the delay happens. > > Yes, I have found the reason for the 3 minute delay: 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 it initializing the snapshots. This is my entire boot log if you need to delve deeper. https://pastebin.com/raw/275JPvZB > Another option is to use systemd-analyze to look into where the time is > going during boot. It has various commands including "plot" which will > generate an SVG plot of the boot timings on stdout. You can then compare > that with a regular boot to try to understand the difference. > Well I don't know about "plot" but this is the output from "systemd-analyze blame" 3min 30.737s dracut-initqueue.service 31.399s udisks2.service 26.650s lvm2-monitor.service 25.500s systemd-journal-flush.service 20.289s ModemManager.service 18.242s abrtd.service 18.233s avahi-daemon.service 18.227s bluetooth.service 17.725s systemd-cryptsetup@luks\x2d2ec7f1ae\x2d6f9b\x2d4896\x2da7b2\x2dbe7809e9d2f4.service 17.604s firewalld.service As you can see the 3min delay matches with the above LVM entry from the boot log. Again, I am very interested in knowing more about these newer snapshots. -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
[linux-lvm] Unusually long boot times with LVM Snapshots
Hi, I use LVM with full disk encryption. I also use LVM snapshots, currently I have a 70GB snapshot. Now the only problem is that the boot times when LVM snapshots are present are extremely long. I boot my machine, enter my encryption passphrase and then wait for about 3 minutes. It is only after that long wait does my machine boot. This only happens if snapshots are present, if no snapshots are present, boot is almost instantaneous after I enter my passphrase. Will adding --skip-mappings help ? Is there any way this can be solved ? -- Regards, Sreyan Chakravarty ___ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
