Bug 2034457

.LVM thin provisioned storage volumes supported as the `vmcore` dump target The `kdump` mechanism now supports thin provisioned logical volumes as the `vmcore` target. To configure LVM thin provisioning, complete the following steps: . Create a LVM volume group. + ---- vgcreate vg00 /dev/sdb ---- . Create a LVM thin pool of 10 MB available space. + ---- lvcreate -L 10M -T vg00/thinpool ---- . Create a LVM thin volume with 300 MB of the file system space. + ---- lvcreate -V 300M -T vg00/thinpool -n thinvol mkfs.ext4 /dev/vg00/thinvol ---- . Configure the LVM thin pool threshold to automatically extend the space. + ---- cat /etc/lvm/lvm.conf activation { thin_pool_autoextend_threshold = 70 thin_pool_autoextend_percent = 20 monitoring = 1 } ---- . Enable the LVM thin pool monitoring service for the first kernel. + ---- systemctl enable lvm2-monitor.service systemctl start lvm2-monitor.service ---- . Append the following lines to the `kdump.conf` file to set the LVM thin volume as the `kdump` target. + ---- ext4 /dev/vg00/thinvol path / ---- . Start the `kdump` service. + ---- kdumpctl restart ---- . Verify the configuration by triggering a kernel panic and check if the `vmcore` is saved to `/dev/vg00/thinvol`. As a result, with this enhancement, the `kdump` mechanism now extends capability to save the `vmcore` dump files on thin provisioned storage volumes.