Back to bug 2083475
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2022-05-10 08:06:49 UTC | Pool ID | sst_kernel_debug_rhel_9 | |
| Red Hat One Jira (issues.redhat.com) | 2022-05-10 08:09:56 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-121533 | |
| Emma Wu | 2022-05-11 00:25:03 UTC | QA Contact | kernel-general-qe | jieli |
| Dave Young | 2022-05-16 06:31:43 UTC | Assignee | kdump-bugs | ltao |
| Dave Young | 2022-05-16 07:00:11 UTC | Summary | [RHEL9.1] Included thin provisioned volume as a supported target for kdump | [RFE][RHEL9.1] Included thin provisioned volume as a supported target for kdump |
| Dave Young | 2022-10-21 06:53:44 UTC | Depends On | 2098500 | |
| Depends On | 2098502 | |||
| Docs Contact | skurup | |||
| errata-xmlrpc | 2022-11-22 08:45:01 UTC | Fixed In Version | kexec-tools-2.0.25-5.el9 | |
| Status | NEW | MODIFIED | ||
| Status | MODIFIED | ON_QA | ||
| Jie Li | 2022-11-23 03:01:23 UTC | Status | ON_QA | VERIFIED |
| Sujata Kurup | 2023-02-21 14:04:17 UTC | Doc Text | .LVM thin provisioned storage volumes supported as the `vmcore` dump target The `kdump` mechanism now supports thin provisioned logical volumes as `vmcore` target. You can create file systems that are greater than the available space in the thin pool. A monitoring service, specifically designed for `kdump`, monitors the thin pool usage and automatically adds more capacity on reaching a set threshold value. As a result, with this enhancement, the `kdump` mechanism now extends capability to save the `vmcore` dump files on thin provisioned storage volumes. |
|
| Sujata Kurup | 2023-02-22 07:21:53 UTC | Doc Text | .LVM thin provisioned storage volumes supported as the `vmcore` dump target The `kdump` mechanism now supports thin provisioned logical volumes as `vmcore` target. You can create file systems that are greater than the available space in the thin pool. A monitoring service, specifically designed for `kdump`, monitors the thin pool usage and automatically adds more capacity on reaching a set threshold value. As a result, with this enhancement, the `kdump` mechanism now extends capability to save the `vmcore` dump files on thin provisioned storage volumes. | .LVM thin provisioned storage volumes supported as the `vmcore` dump target The `kdump` mechanism now supports thin provisioned logical volumes as the `vmcore` target. You can create file systems that are greater than the available space in the thin pool. A monitoring service, specifically designed for `kdump`, monitors the thin pool usage and automatically adds more capacity on reaching a set threshold value. To configure LVM thin provisioning: . 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 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. |
| Sujata Kurup | 2023-02-22 07:26:37 UTC | Flags | needinfo?(jieli) | |
| Dave Young | 2023-02-22 08:17:27 UTC | Flags | needinfo?(jieli) | needinfo?(ltao) |
| Sujata Kurup | 2023-02-23 12:37:35 UTC | CC | skurup | |
| Flags | needinfo?(ltao) | |||
| Flags | needinfo?(skurup) | |||
| Doc Text | .LVM thin provisioned storage volumes supported as the `vmcore` dump target The `kdump` mechanism now supports thin provisioned logical volumes as the `vmcore` target. You can create file systems that are greater than the available space in the thin pool. A monitoring service, specifically designed for `kdump`, monitors the thin pool usage and automatically adds more capacity on reaching a set threshold value. To configure LVM thin provisioning: . 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 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. | .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: . 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 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. |
||
| Sujata Kurup | 2023-02-27 09:00:17 UTC | Flags | needinfo?(skurup) | |
| errata-xmlrpc | 2023-05-09 00:20:50 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-05-09 08:14:36 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-05-09 08:14:36 UTC | |||
| errata-xmlrpc | 2023-05-09 08:14:55 UTC | Link ID | Red Hat Product Errata RHBA-2023:2463 | |
| Sujata Kurup | 2023-07-28 07:31:49 UTC | CC | ttuffin | |
| Flags | needinfo?(ltao) |
Back to bug 2083475