Back to bug 801571
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Milan Broz | 2012-03-08 22:01:19 UTC | Assignee | lvm-team | jbrassow |
| Corey Marthaler | 2012-03-08 22:33:45 UTC | Keywords | TestBlocker | |
| Jonathan Earl Brassow | 2012-03-12 19:56:40 UTC | Status | NEW | ASSIGNED |
| Flags | needinfo?(cmarthal) | |||
| Corey Marthaler | 2012-03-12 21:41:24 UTC | Flags | needinfo?(cmarthal) | |
| Corey Marthaler | 2012-03-14 22:36:14 UTC | Status | ASSIGNED | CLOSED |
| Resolution | --- | WORKSFORME | ||
| Last Closed | 2012-03-14 18:36:14 UTC | |||
| Corey Marthaler | 2012-11-07 17:10:09 UTC | Status | CLOSED | ASSIGNED |
| Resolution | WORKSFORME | --- | ||
| Keywords | Reopened | |||
| Suzanne Logcher | 2012-11-20 16:44:10 UTC | CC | syeghiay | |
| Jonathan Earl Brassow | 2012-11-28 17:20:04 UTC | Flags | needinfo?(cmarthal) | |
| Jonathan Earl Brassow | 2012-11-30 17:40:58 UTC | Status | ASSIGNED | POST |
| Marian Csontos | 2012-12-05 09:03:53 UTC | CC | mcsontos | |
| Corey Marthaler | 2012-12-06 19:49:17 UTC | Flags | needinfo?(cmarthal) | |
| Peter Rajnoha | 2012-12-11 11:01:35 UTC | Flags | needinfo?(cmarthal) | |
| Marian Csontos | 2012-12-11 11:55:07 UTC | Flags | needinfo?(jbrassow) | |
| Corey Marthaler | 2012-12-14 23:19:08 UTC | Flags | needinfo?(cmarthal) needinfo?(jbrassow) | |
| Peter Rajnoha | 2012-12-17 09:27:01 UTC | Status | POST | ASSIGNED |
| Jonathan Earl Brassow | 2012-12-18 20:42:56 UTC | Status | ASSIGNED | POST |
| Peter Rajnoha | 2012-12-20 13:03:56 UTC | Status | POST | MODIFIED |
| Fixed In Version | lvm2-2.02.98-6.el6 | |||
| errata-xmlrpc | 2012-12-20 13:06:41 UTC | Status | MODIFIED | ON_QA |
| Corey Marthaler | 2012-12-20 22:08:52 UTC | Status | ON_QA | VERIFIED |
| releng-rhel | 2013-01-15 18:02:11 UTC | Blocks | 895654 | |
| Jonathan Earl Brassow | 2013-02-07 16:43:19 UTC | Doc Text | Previously, if a device failed while a RAID logical volume was not in-sync, any attempts to fix it would fail in an uncontroled way. This case is now handled but there are some changes that must be noted: 1) You cannot repair or replace devices in a RAID logical volume that is not active. The tool ('lvconvert --repair') must know the sync status of the array and can only get that when the array is active. 2) You cannot replace a device in a RAID logical volume that has not completed its initial synchronization. Doing so would produce unpredictable results and is therefore disallowed. 3) You can repair a RAID logical volume that has not completed its initial synchronization, but some data may not be recoverable because it had not had time to make that data fully redundant. In this case, a warning is printed and the user is queried if they would like to proceed. |
|
| Alasdair Kergon | 2013-02-07 17:14:24 UTC | Doc Text | Previously, if a device failed while a RAID logical volume was not in-sync, any attempts to fix it would fail in an uncontroled way. This case is now handled but there are some changes that must be noted: 1) You cannot repair or replace devices in a RAID logical volume that is not active. The tool ('lvconvert --repair') must know the sync status of the array and can only get that when the array is active. 2) You cannot replace a device in a RAID logical volume that has not completed its initial synchronization. Doing so would produce unpredictable results and is therefore disallowed. 3) You can repair a RAID logical volume that has not completed its initial synchronization, but some data may not be recoverable because it had not had time to make that data fully redundant. In this case, a warning is printed and the user is queried if they would like to proceed. | Previously, if a device failed while a RAID logical volume was not in-sync, any attempts to fix it would fail in an uncontrolled way. This case is now handled but there are some changes that must be noted: 1) You cannot repair or replace devices in a RAID logical volume that is not active. The tool ('lvconvert --repair') must know the sync status of the array and can only get that when the array is active. 2) You cannot replace a device in a RAID logical volume that has not completed its initial synchronization. Doing so would produce unpredictable results and is therefore disallowed. 3) You can repair a RAID logical volume that has not completed its initial synchronization, but some data may not be recoverable because it had not had time to make that data fully redundant. In this case, a warning is printed and the user is queried if they would like to proceed. |
| errata-xmlrpc | 2013-02-21 08:03:36 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2012-03-14 18:36:14 UTC | 2013-02-21 03:03:36 UTC |
Back to bug 801571