man: mention system ID in vgexport and vgimport

diff --git a/man/vgexport.8.in b/man/vgexport.8.in
index 94a3e32540514eb4d1b2f64df54d4f6656453de6..08c1d780e6731060a99dc1108d4b5f4dd7630463 100644 (file)
--- 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 3a8a230b82dead2ae7d4d189540fc67f22b5ee2f..cd3404968746db52afe6b2f9d3293657136732ef 100644 (file)
--- 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)