Back to bug 1016218
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Corey Marthaler | 2013-10-07 17:51:03 UTC | Priority | unspecified | low |
| Zdenek Kabelac | 2013-10-22 08:03:37 UTC | Assignee | lvm-team | prajnoha |
| Peter Rajnoha | 2013-11-26 14:02:36 UTC | Status | NEW | POST |
| Nitin Yewale | 2013-12-19 19:19:56 UTC | CC | nyewale | |
| Link ID | Red Hat Knowledge Base (Solution) 650503 | |||
| Corey Marthaler | 2014-04-07 21:27:51 UTC | Blocks | 1085119 | |
| Peter Rajnoha | 2014-06-23 14:52:50 UTC | Status | POST | MODIFIED |
| Fixed In Version | lvm2-2.02.107-1.el6 | |||
| errata-xmlrpc | 2014-06-23 14:57:23 UTC | Status | MODIFIED | ON_QA |
| Nenad Peric | 2014-07-15 14:30:26 UTC | Status | ON_QA | VERIFIED |
| CC | nperic | |||
| Lubos Kocman | 2014-07-22 17:07:22 UTC | Depends On | 1122165 | |
| John Shortt | 2014-07-22 17:57:00 UTC | Depends On | 1122165 | |
| Peter Rajnoha | 2014-09-11 09:03:37 UTC | Doc Text | Cause: LVM tools tried to connect to lvmetad even though the tools were run with the --sysinit option to denote the early system initialization where lvmetad may not have been running yet. Consequence: There were error messages "lvmetad.socket: connect failed: No such file or directory" issued multiple times during system initialization. Fix: There's an additional check whether LVM tool is running during early system initialization by checking the use of --sysinit option which is used in such cases. Result: If there's no lvmetad socket present while in early system initialization (while using --sysinit LVM command option), no error messages are issued about missing lvmetad socket if this is detected and LVM tools automatically fallback to non-lvmetad mode silently. |
|
| Alasdair Kergon | 2014-09-18 23:06:20 UTC | Sub Component | LVM Metadata / lvmetad (RHEL6) | |
| errata-xmlrpc | 2014-10-14 08:24:43 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-10-14 04:24:43 UTC |
Back to bug 1016218