Re: [linux-lvm] Is TRIM and DISCARD needed for normal HDD ?
Title: Re: [linux-lvm] Is TRIM and DISCARD needed for normal HDD ? Hi, TRIM is also used on some SMR HDDs. https://superuser.com/questions/1407990/what-does-trim-on-an-hdd-mean Wednesday, November 25, 2020, 16:37:07, you wrote: 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 -- bYE, Marki ___ 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] Is TRIM and DISCARD needed for normal HDD ?
Dne 25. 11. 20 v 16:37 Sreyan Chakravarty napsal(a): 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 ? Hi Thin-pool is created by default with 'passdown' TRIM/discard support. This means - discard to thin LV (i.e. fstrim of ext4 on thinLV) gets propagated to thin-pool, where it may deallocate full chunk when possible (i.e. if you use 256K chunk, WHOLE chunk must be free to have an effective discard). With "passdown" mode - such released chunks are also then passed through to origin _tdata device - where again some 'alignment rules' of discardable regions applie (i.e. lot of SSD need 512KiB blocks). If you have HDD - then clearly such discard stops at thin-pool level (automatically) and just releases chunks in thin-pool for future reuse. "ignore" discard mode is usefull in the case you want to keep already 'allocated' chunks for thin LV always there - and also in some case it may make timing more predictible - as discard requires processing - so it ma slowdown few things - but at the expense of more filled thin-pool Hopefully this makes it clear. Regards Zdenek ___ 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/
