mirror of
git://sourceware.org/git/lvm2.git
synced 2025-03-10 16:58:47 +03:00
82d83a01ce
When autoactivating a VG, there could be an existing VG with exactly the same PV UUIDs. The PVs could be reappeared after previous loss/disconnect (for example disconnecting and reconnecting iscsi). Since there's no "autodeactivation" yet, the mappings for the LVs from the VG were left in the system even if the device was disconnected. These mappings also hold the major:minor of the underlying device. So if the device reappears, it is assigned a different major:minor pair (...and kernel name). We need to cope with this during autoactivation so any existing mappings are corrected for any changes. The VG refresh does that (the vgchange --refresh functionality) - call this before VG autoactivation. (If the VG does not exist yet, the VG refresh is NOP)
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://sources.redhat.com/pub/lvm2/ The source code is stored in git: http://git.fedorahosted.org/git/lvm2.git git clone git://git.fedorahosted.org/git/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/linux-lvm 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 The source code repository used until 7th June 2012 is accessible here: http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/?cvsroot=lvm2.