Back to bug 1380521
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Corey Marthaler | 2016-10-03 18:54:05 UTC | Summary | conversion repair deadlock after mirror device failure | mirror type conversion/repair deadlock after device failure (device-mapper: raid1: Write error during recovery) |
| Corey Marthaler | 2016-10-04 17:06:59 UTC | Keywords | Regression | |
| Jonathan Earl Brassow | 2016-10-05 19:23:54 UTC | Assignee | lvm-team | heinzm |
| Jonathan Earl Brassow | 2016-10-05 19:52:39 UTC | Attachment #1207668 Attachment is obsolete | 0 | 1 |
| Jonathan Earl Brassow | 2016-10-07 14:34:54 UTC | Keywords | ZStream | |
| Heinz Mauelshagen | 2016-10-10 14:12:07 UTC | Status | NEW | ASSIGNED |
| Jonathan Earl Brassow | 2016-10-10 20:54:22 UTC | Doc Text | When the legacy 'mirror' segment type is used to create mirrored logical volumes with 3 or more legs, there can be interaction problems with 'lvmetad'. (The new "raid1" segment type is the default type used in RHEL7 and does not suffer from these issues.) The simplest workaround is to disable lvmetad by setting 'use_lvmetad = 0' in the lvm.conf file. Problems observed occur only after a second device failure, when mirror fault policies are set to the non-default "allocate" option, when lvmetad is used, and there has been no reboot of the machine between device failure events. | |
| Doc Type | If docs needed, set a value | Known Issue | ||
| Mark Thacker | 2016-10-11 00:29:39 UTC | CC | mthacker | |
| Steven J. Levine | 2016-10-13 12:52:01 UTC | CC | slevine | |
| Docs Contact | slevine | |||
| Steven J. Levine | 2016-10-13 16:19:05 UTC | Doc Text | When the legacy 'mirror' segment type is used to create mirrored logical volumes with 3 or more legs, there can be interaction problems with 'lvmetad'. (The new "raid1" segment type is the default type used in RHEL7 and does not suffer from these issues.) The simplest workaround is to disable lvmetad by setting 'use_lvmetad = 0' in the lvm.conf file. Problems observed occur only after a second device failure, when mirror fault policies are set to the non-default "allocate" option, when lvmetad is used, and there has been no reboot of the machine between device failure events. | Interaction problems with the `lvmetad` daemon when `mirror` segment type is used. When the legacy 'mirror' segment type is used to create mirrored logical volumes with 3 or more legs, there can be interaction problems with the 'lvmetad' daemon. Problems observed occur only after a second device failure, when mirror fault policies are set to the non-default `allocate` option, when `lvmetad` is used, and there has been no reboot of the machine between device failure events. The simplest workaround is to disable `lvmetad` by setting 'use_lvmetad = 0' in the `lvm.conf` file. These issues do not arise with the `raid1` segment type, which is the default type for Red Hat Enterprise Linux 7. |
| Jonathan Earl Brassow | 2016-10-18 13:30:31 UTC | Keywords | ZStream | |
| Priority | unspecified | high | ||
| Lenka Špačková | 2016-11-23 13:19:20 UTC | Doc Text | Interaction problems with the `lvmetad` daemon when `mirror` segment type is used. When the legacy 'mirror' segment type is used to create mirrored logical volumes with 3 or more legs, there can be interaction problems with the 'lvmetad' daemon. Problems observed occur only after a second device failure, when mirror fault policies are set to the non-default `allocate` option, when `lvmetad` is used, and there has been no reboot of the machine between device failure events. The simplest workaround is to disable `lvmetad` by setting 'use_lvmetad = 0' in the `lvm.conf` file. These issues do not arise with the `raid1` segment type, which is the default type for Red Hat Enterprise Linux 7. | Interaction problems with the *lvmetad* daemon when `mirror` segment type is used. When the legacy `mirror` segment type is used to create mirrored logical volumes with 3 or more legs, there can be interaction problems with the *lvmetad* daemon. Problems observed occur only after a second device failure, when mirror fault policies are set to the non-default `allocate` option, when *lvmetad* is used, and there has been no reboot of the machine between device failure events. The simplest workaround is to disable *lvmetad* by setting `use_lvmetad = 0` in the `lvm.conf` file. These issues do not arise with the `raid1` segment type, which is the default type for Red Hat Enterprise Linux 7. |
| Jonathan Earl Brassow | 2016-12-21 20:36:04 UTC | Blocks | 1385242 | |
| Heinz Mauelshagen | 2017-03-09 19:42:14 UTC | Status | ASSIGNED | POST |
| Jaroslav Reznik | 2017-03-10 13:12:35 UTC | CC | jreznik | |
| Jaroslav Reznik | 2017-03-10 13:12:55 UTC | Blocks | 1431146 | |
| Jaroslav Reznik | 2017-03-10 13:13:41 UTC | Keywords | ZStream | |
| Marian Csontos | 2017-03-28 15:41:36 UTC | Status | POST | MODIFIED |
| Fixed In Version | lvm2-2.02.169-1.el7 | |||
| errata-xmlrpc | 2017-03-28 15:46:47 UTC | Status | MODIFIED | ON_QA |
| Marian Csontos | 2017-04-27 14:01:05 UTC | CC | mcsontos | |
| Flags | needinfo?(heinzm) | |||
| Roman Bednář | 2017-05-10 08:18:53 UTC | CC | rbednar | |
| Roman Bednář | 2017-05-10 08:19:21 UTC | Status | ON_QA | VERIFIED |
| Heinz Mauelshagen | 2017-06-23 11:14:59 UTC | Flags | needinfo?(heinzm) | |
| Lenka Špačková | 2017-07-14 20:30:02 UTC | Doc Text | Interaction problems with the *lvmetad* daemon when `mirror` segment type is used. When the legacy `mirror` segment type is used to create mirrored logical volumes with 3 or more legs, there can be interaction problems with the *lvmetad* daemon. Problems observed occur only after a second device failure, when mirror fault policies are set to the non-default `allocate` option, when *lvmetad* is used, and there has been no reboot of the machine between device failure events. The simplest workaround is to disable *lvmetad* by setting `use_lvmetad = 0` in the `lvm.conf` file. These issues do not arise with the `raid1` segment type, which is the default type for Red Hat Enterprise Linux 7. | Interaction problems no longer occur with the *lvmetad* daemon when `mirror` segment type is used Previously, when the legacy `mirror` segment type was used to create mirrored logical volumes with 3 or more legs, interaction problems could occur with the *lvmetad* daemon. Problems observed occurred only after a second device failure, when mirror fault policies were set to the non-default `allocate` option, when *lvmetad* was used, and there had been no reboot of the machine between device failure events. This bug has been fixed, and the described interaction problems no longer occur. |
| Doc Type | Known Issue | Bug Fix | ||
| errata-xmlrpc | 2017-08-01 21:47:18 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-08-01 17:47:18 UTC | |||
| Pasi Karkkainen | 2017-08-02 08:13:13 UTC | CC | pasik | |
| Pavel Najman | 2021-09-03 12:56:19 UTC | Pool ID | sst_platform_storage_rhel_7 | sst_logical_storage_rhel_7 |
Back to bug 1380521