Back to bug 1240549
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Peter Rajnoha | 2015-07-07 08:42:19 UTC | Blocks | 1163895 | |
| Corey Marthaler | 2015-07-07 13:40:51 UTC | CC | cmarthal | |
| Jonathan Earl Brassow | 2016-01-22 15:27:21 UTC | Blocks | 1295577 | |
| Roman Bednář | 2016-02-10 10:28:23 UTC | CC | rbednar | |
| Libor Miksik | 2016-03-01 17:43:57 UTC | Blocks | 1313485 | |
| Peter Rajnoha | 2016-03-14 13:20:14 UTC | Status | ASSIGNED | POST |
| Sat6QE Jenkins | 2016-03-28 20:15:54 UTC | Status | POST | MODIFIED |
| Mike McCune | 2016-03-28 23:21:47 UTC | Status | MODIFIED | POST |
| Peter Rajnoha | 2016-05-04 13:31:54 UTC | Status | POST | MODIFIED |
| Fixed In Version | lvm2-2.02.152-1.el7 | |||
| errata-xmlrpc | 2016-05-04 13:45:22 UTC | Status | MODIFIED | ON_QA |
| Roman Bednář | 2016-07-20 13:27:06 UTC | Status | ON_QA | VERIFIED |
| Peter Rajnoha | 2016-08-15 11:50:00 UTC | Doc Text | LVM2 now provides a way to track already removed LVs when enabled with metadata/record_lvs_history=1 lvm.conf setting. This feature is currently available for thin snapshot LVs only. With this, it's also possible to to track thin snapshot dependency chain even after an LV is removed from the original chain and it becomes historical LV. The full dependency chain, including historical LVs, can be displayed with new lv_full_ancestors and lv_full_descendants reporting fields. lvs and lvdisplay reporting commands gained new -H|--history option to include historical LVs in the output as well as lvremove to make it possible to process and remove historical LVs. Also, historical LVs can be removed automatically by defining the retention time with metadata/lvs_history_retention_time lvm.conf setting. | |
| Doc Type | Bug Fix | Enhancement | ||
| Peter Rajnoha | 2016-08-15 12:02:46 UTC | Doc Text | LVM2 now provides a way to track already removed LVs when enabled with metadata/record_lvs_history=1 lvm.conf setting. This feature is currently available for thin snapshot LVs only. With this, it's also possible to to track thin snapshot dependency chain even after an LV is removed from the original chain and it becomes historical LV. The full dependency chain, including historical LVs, can be displayed with new lv_full_ancestors and lv_full_descendants reporting fields. lvs and lvdisplay reporting commands gained new -H|--history option to include historical LVs in the output as well as lvremove to make it possible to process and remove historical LVs. Also, historical LVs can be removed automatically by defining the retention time with metadata/lvs_history_retention_time lvm.conf setting. | LVM2 now provides a way to track already removed LVs when enabled with metadata/record_lvs_history=1 lvm.conf setting. This feature is currently available for thin snapshot LVs only. With this, it's also possible to track thin snapshot dependency chain even after an LV is removed from the original chain and it becomes a historical LV. The full dependency chain, including historical LVs, can be displayed with new lv_full_ancestors and lv_full_descendants reporting fields. lvs and lvdisplay reporting commands gained new -H|--history option to include historical LVs in the output as well as lvremove to make it possible to process and remove historical LVs. Also, historical LVs can be removed automatically by defining the retention time with metadata/lvs_history_retention_time lvm.conf setting. |
| errata-xmlrpc | 2016-11-02 12:11:28 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-11-04 04:09:58 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-11-04 00:09:58 UTC | |||
| Steven J. Levine | 2017-03-28 15:14:34 UTC | CC | slevine | |
| Doc Text | LVM2 now provides a way to track already removed LVs when enabled with metadata/record_lvs_history=1 lvm.conf setting. This feature is currently available for thin snapshot LVs only. With this, it's also possible to track thin snapshot dependency chain even after an LV is removed from the original chain and it becomes a historical LV. The full dependency chain, including historical LVs, can be displayed with new lv_full_ancestors and lv_full_descendants reporting fields. lvs and lvdisplay reporting commands gained new -H|--history option to include historical LVs in the output as well as lvremove to make it possible to process and remove historical LVs. Also, historical LVs can be removed automatically by defining the retention time with metadata/lvs_history_retention_time lvm.conf setting. | LVM can now track and display thin snapshot logical volumes that have been removed You can now configure your system to track thin snapshot logical volumes that have been removed by enabling the `record_lvs_history` metadata option in the `lvm.conf` configuration file. This allows you to display a full thin snapshot dependency chain that includes logical volumes that have been removed from the original dependency chain and have become historical logical volumes. The full dependency chain, including historical LVs, can be displayed with new lv_full_ancestors and lv_full_descendants reporting fields. For information on configuring and displaying historical logical volumes, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Logical_Volume_Manager_Administration/LV.html#historical_volumes | ||
| Flags | needinfo?(prajnoha) | |||
| Peter Rajnoha | 2017-03-29 07:05:57 UTC | Flags | needinfo?(prajnoha) | |
| Pavel Najman | 2021-09-03 12:52:38 UTC | Pool ID | sst_platform_storage_rhel_7 | sst_logical_storage_rhel_7 |
| RHEL Program Management | 2023-03-08 07:27:39 UTC | Keywords | Triaged |
Back to bug 1240549