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 857530 - Document lvmetad in 6.4, if deemed necessary for users
Summary: Document lvmetad in 6.4, if deemed necessary for users
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Logical_Volume_Manager
Version: 6.0
Hardware: All
OS: Linux
high
medium
Target Milestone: beta
: 6.3
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 464877
Blocks: 464724 697866 705085 718103 756082
TreeView+ depends on / blocked
 
Reported: 2012-09-14 18:40 UTC by Steven J. Levine
Modified: 2013-02-25 18:30 UTC (History)
24 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 464877
Environment:
Last Closed: 2013-02-25 18:30:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 3 Steven J. Levine 2012-10-10 00:11:21 UTC 
From me:

Ok, I'll try to follow up in a couple of weeks about the status of the command (re: tech. preview) and follow these guidelines for documentation if it is out of tech. preview for 6.4.

-Steven
Comment 6 Nenad Peric 2012-10-25 06:40:08 UTC 
Passed basic LVM tests with lvmetad/use_lvmetad turned on. 

Verifying as SanityOnly. 

lvm2-libs-2.02.98-2.el6.x86_64
lvm2-2.02.98-2.el6.x86_64
lvm2-cluster-2.02.98-2.el6.x86_64

device-mapper-1.02.77-2.el6.x86_64
device-mapper-libs-1.02.77-2.el6.x86_64
device-mapper-event-1.02.77-2.el6.x86_64
device-mapper-event-libs-1.02.77-2.el6.x86_64

cmirror-2.02.98-2.el6.x86_64

kernel-firmware-2.6.32-330.el6.noarch
Comment 7 Steven J. Levine 2012-11-19 21:57:32 UTC 
I'm re-opening this bug, since it is a doc bug and I need to be sure that the documentation is correct (and verified).

Also the bug is assigned to me.  Since I didn't have the information for this feature until after the development period I'm exceptioning this bug.

I have a draft of what I have added to the LVM document that I will be sending to Petr for his ok.
Comment 10 Petr Rockai 2012-11-20 23:20:16 UTC 
I have drafted the following text, presumably would work as a new section, 3.6 Metadata Daemon:

LVM can optionally use a central metadata cache, implemented
through a daemon (lvmetad) and an udev rule. The metadata daemon
has two main purposes: it improves performance of LVM commands
and it allows udev to automatically activate logical volumes or
entire volume groups as they become available to the system.

To take advantage of the daemon, it needs to be started through
the "lvm2-lvmetad" service: use "chkconfig lvm2-lvmetad on" to
start the daemon automatically at boot time, and "service
lvm2-lvmetad start" to start it manually. Moreover, LVM needs to
be configured to make use of the daemon. To this effect, set the
lvm.conf variable "global/use_lvmetad" to 1.

Normally, each LVM command issues a disk scan to find all
relevant physical volumes and to read volume group
metadata. However, if the metadata daemon is running and enabled,
this expensive scan can be skipped: lvmetad scans each device
only once, when it becomes available, via udev rules. Especially
on systems with many disks, this can save significant amount of
I/O and reduce the time required to complete LVM operations.

When a new volume group is made available at runtime (eg. through
hotplug or iSCSI), its logical volumes must be activated in order
to be used. When lvmetad is enabled,
the "activation/auto_activation_volume_list" lvm.conf option can
be used to configure a list of volume groups and/or logical
volumes that should be automatically activated. Without lvmetad,
a manual activation is necessary.
Note You need to log in before you can comment on or make changes to this bug.