mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-22 17:35:59 +03:00
LVM2 mirror repository
https://sourceware.org/lvm2/
8bcd482cc5
Use temp files in /run/lvm/vgs_online/ to keep track of when a VG has been autoactivated by pvscan. When pvscan autoactivates a VG, it creates a temp file with the VG's name. Before a subsequent pvscan tries to autoactivate the same VG, it checks if a temp file exists for the VG name, and if so it skips it. This can commonly happen when many devices appear on the system at once, which generates several concurrent pvscans. In this case the first pvscan does initialization by scanning all devices and activating any complete VGs. The other pvscans would attempt to activate the same complete VGs again. This extra work could create a bottleneck of pvscan commands. If a VG is deactivated by vgchange, the vg online file is removed. If PVs are then disconnected/reconnected, pvscan will again autoactivate the VG. Also, this patch disables the VG refresh that could be called from pvscan --cache -aay if lvmetad detects metadata inconsistencies. The role of pvscan should be limited to basic autoactivation, and any refresh scenarios are special cases that are not appropriate for automation. The warning printed by commands retrying an lvmetad connection has been reduced to once every 10 seconds. New output messages have been added to pvscan to record when pvscan is falling back to direct activation of all VGs. |
||
---|---|---|
autoconf | ||
base | ||
conf | ||
coverity | ||
daemons | ||
device_mapper | ||
doc | ||
include | ||
lib | ||
libdaemon | ||
libdm | ||
liblvm | ||
man | ||
nix | ||
po | ||
python | ||
scripts | ||
spec | ||
test | ||
tools | ||
udev | ||
.gitignore | ||
acinclude.m4 | ||
aclocal.m4 | ||
configure | ||
configure.ac | ||
COPYING | ||
COPYING.BSD | ||
COPYING.LIB | ||
INSTALL | ||
make.tmpl.in | ||
Makefile.in | ||
README | ||
TESTING | ||
VERSION | ||
VERSION_DM | ||
WHATS_NEW | ||
WHATS_NEW_DM |
This tree contains the LVM2 and device-mapper tools and libraries. For more information about LVM2 read the changelog in the WHATS_NEW file. Installation instructions are in INSTALL. There is no warranty - see COPYING and COPYING.LIB. Tarballs are available from: ftp://sourceware.org/pub/lvm2/ ftp://sources.redhat.com/pub/lvm2/ https://github.com/lvmteam/lvm2/releases The source code is stored in git: https://sourceware.org/git/?p=lvm2.git git clone git://sourceware.org/git/lvm2.git mirrored to: https://github.com/lvmteam/lvm2 git clone https://github.com/lvmteam/lvm2.git git clone git@github.com:lvmteam/lvm2.git Mailing list for general discussion related to LVM2: linux-lvm@redhat.com Subscribe from https://www.redhat.com/mailman/listinfo/linux-lvm Mailing lists for LVM2 development, patches and commits: lvm-devel@redhat.com Subscribe from https://www.redhat.com/mailman/listinfo/lvm-devel lvm2-commits@lists.fedorahosted.org (Read-only archive of commits) Subscribe from https://fedorahosted.org/mailman/listinfo/lvm2-commits Mailing list for device-mapper development, including kernel patches and multipath-tools: dm-devel@redhat.com Subscribe from https://www.redhat.com/mailman/listinfo/dm-devel Website: https://sourceware.org/lvm2/ Report upstream bugs at: https://bugzilla.redhat.com/enter_bug.cgi?product=LVM%20and%20device-mapper or open issues at: https://github.com/lvmteam/lvm2/issues The source code repository used until 7th June 2012 is accessible here: http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/?cvsroot=lvm2.