Back to bug 1311765
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Corey Marthaler | 2016-02-24 23:49:53 UTC | Keywords | Regression, TestBlocker | |
| Jonathan Earl Brassow | 2016-03-02 15:22:58 UTC | Assignee | lvm-team | heinzm |
| Heinz Mauelshagen | 2016-03-02 20:19:18 UTC | Status | NEW | ASSIGNED |
| Corey Marthaler | 2016-04-06 18:30:24 UTC | Keywords | Regression, TestBlocker | |
| Peter Rajnoha | 2016-11-08 13:44:24 UTC | Status | ASSIGNED | POST |
| Peter Rajnoha | 2016-11-09 15:49:33 UTC | Status | POST | MODIFIED |
| Fixed In Version | lvm2-2.02.143-8.el6 | |||
| errata-xmlrpc | 2016-11-09 15:51:30 UTC | Status | MODIFIED | ON_QA |
| Heinz Mauelshagen | 2016-11-23 23:15:21 UTC | Doc Text | Cause: Data loss on converted linear LV to raid1. A failed primary raid1 leg during initial resynchronization of an upconverted linear LV (e.g "lvconvert -m1 $LinearLV") could be replaced, thus losing the previous linear LV and any of its still recoverable data. Consequence: Any still recoverable data on the primary, previously linear leg is lost. Fix: Reject repair of a raid1 with failed primary leg during initial synchronization. Result: A monitored raid1 LV is not silently repaired any more. When repairing manually, a message is displayed that repair is only possible using --force thus enabling the user to do data recovery on any still partially readable primary leg. |
|
| Heinz Mauelshagen | 2016-11-23 23:16:10 UTC | Doc Type | Bug Fix | Enhancement |
| Heinz Mauelshagen | 2016-11-23 23:17:47 UTC | Blocks | 1397589 | |
| Corey Marthaler | 2016-11-30 20:20:36 UTC | Status | ON_QA | VERIFIED |
| Summary | non synced raid recovery allocation unable to take place | non synced primary leg raid1 recovery allocation unable to take place | ||
| errata-xmlrpc | 2017-03-21 01:43:12 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-03-21 12:02:26 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-03-21 08:02:26 UTC | |||
| Heinz Mauelshagen | 2017-05-12 14:10:10 UTC | Blocks | 1446754 |
Back to bug 1311765