RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 817776 - Improve resilience & robustness of lvmetad
Summary: Improve resilience & robustness of lvmetad
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.4
Hardware: All
OS: Linux
high
medium
Target Milestone: pre-dev-freeze
: 6.4
Assignee: Petr Rockai
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On: 813766 814782 823660 823667 823918
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-01 08:41 UTC by Alasdair Kergon
Modified: 2012-11-19 15:56 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-19 15:56:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alasdair Kergon 2012-05-01 08:41:02 UTC 
Consider all failure modes and improve/document handling wherever possible.

Ensure all relevant internal state is easily available in support situations e.g. via lvmdump.
Comment 2 Alasdair Kergon 2012-05-01 14:28:06 UTC 
Documentation might include: man page, docs team guide, knowledge base.

Internal state might be dumped via signal and/or client commands.

Review & extend/reduce log messages.

Failure modes incl. daemon dying/freezing, uevents getting lost/internal state inconsistent (incl. e.g. a missed 'remove' event)
Comment 3 Petr Rockai 2012-05-20 12:55:52 UTC 
I think that this BZ needs to be broken up into actual tasks. Ideas:
- debug and non-debug logging
- on-demand state dump (for lvmdump &c.)
- documentation of failure modes out of our control (udev bugs)
- user level documentation (but I need to know what is actually missing? we
  have example.conf and a manpage, maybe need to update the LVM guide?)
Comment 4 Alasdair Kergon 2012-05-21 00:34:28 UTC 
Yes, new bugs for each of those and set them to 'block' this bug.
Then change the Keyword on this bug from 'FutureFeature' to 'Tracking'.  (The new bugs will themselves be 'FutureFeature'.)
Comment 5 Peter Rajnoha 2012-05-22 13:05:21 UTC 
Just an instance of the problem related to resilience/robustness: bug #823918.
Comment 8 Petr Rockai 2012-10-12 09:04:40 UTC 
the sub-BZs of this have been all POST'd now, what remains to do is documentation. I'll POST this BZ as soon as that's done. I think we are on track to move lvmetad out of tech preview for 6.4, pending QA results...
Comment 9 Petr Rockai 2012-11-19 15:56:39 UTC 
Things seem to be going well so far. I have checked in some upstream doc updates. The handbook is in Steve's hands, and I believe he has the info he needs. Therefore, I'm closing this one.
Note You need to log in before you can comment on or make changes to this bug.