From: David Teigland <teigland@redhat.com>
Date: Fri, 7 Aug 2015 21:35:07 +0000 (-0500)
Subject: man: mention system ID in vgexport and vgimport
X-Git-Tag: v2_02_127~9
X-Git-Url: https://sourceware.org/git/?a=commitdiff_plain;h=b59cdf089217e1b86b2106bdccb990bda92690e5;p=lvm2.git

man: mention system ID in vgexport and vgimport
---

diff --git a/man/vgexport.8.in b/man/vgexport.8.in
index 94a3e3254..08c1d780e 100644
--- a/man/vgexport.8.in
+++ b/man/vgexport.8.in
@@ -20,6 +20,8 @@ You can then move all the Physical Volumes in that Volume Group to
 a different system for later
 .BR vgimport (8).
 Most LVM2 tools ignore exported Volume Groups.
+vgexport clears the VG system ID, and vgimport sets the VG system ID
+to match the host running vgimport (if the host has a system ID).
 .SH OPTIONS
 See \fBlvm\fP(8) for common options.
 .TP
@@ -29,4 +31,5 @@ Export all inactive Volume Groups.
 .BR lvm (8),
 .BR pvscan (8),
 .BR vgimport (8),
-.BR vgscan (8)
+.BR vgscan (8),
+.BR lvmsystemid (7)
diff --git a/man/vgimport.8.in b/man/vgimport.8.in
index 3a8a230b8..cd3404968 100644
--- a/man/vgimport.8.in
+++ b/man/vgimport.8.in
@@ -16,6 +16,8 @@ exported using
 .BR vgexport (8)
 known to the system again, perhaps after moving its Physical Volumes
 from a different machine.
+vgexport clears the VG system ID, and vgimport sets the VG system ID
+to match the host running vgimport (if the host has a system ID).
 .SH OPTIONS
 See \fBlvm\fP(8) for common options.
 .TP
@@ -30,4 +32,5 @@ failed and they cannot be restored.
 .BR lvm (8),
 .BR pvscan (8),
 .BR vgexport (8),
-.BR vgscan (8)
+.BR vgscan (8),
+.BR lvmsystemid (7)