Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2083475

Summary: [RFE][RHEL9.1] Included thin provisioned volume as a supported target for kdump
Product: Red Hat Enterprise Linux 9 Reporter: ltao
Component: kexec-toolsAssignee: ltao
Status: CLOSED ERRATA QA Contact: Jie Li <jieli>
Severity: medium Docs Contact: Sujata Kurup <skurup>
Priority: unspecified    
Version: 9.1CC: agk, gfialova, heinzm, jbrassow, jieli, ltao, msnitzer, mwest, pdwyer, prajnoha, ruyang, skurup, thornber, xiawu, zkabelac
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: kexec-tools-2.0.25-5.el9 Doc Type: Enhancement
Doc Text:
.LVM thin provisioning storage volumes supported as the `vmcore` dump target The `kdump` mechanism now supports thin provisioning logical volumes as the `vmcore` target. To configure LVM thin provisioning, complete the following steps: . Create an LVM volume group. + ---- vgcreate vg00 /dev/sdb ---- . Create an LVM thin pool of 10 MB available space. + ---- lvcreate -L 10M -T vg00/thinpool ---- . Create an 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 provisioning storage volumes.
Story Points: ---
Clone Of: 2034457 Environment:
Last Closed: 2023-05-09 08:14:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2034457, 2098500, 2098502    
Bug Blocks:    

Comment 19 errata-xmlrpc 2023-05-09 08:14:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (kexec-tools bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2463