shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2025-01-18 10:04:20 +03:00
Code Releases Activity

man lvmsystemid: fix typos

Browse Source
This commit is contained in:
David Teigland 2015-10-08 13:21:42 -05:00
parent c9ff5c8223
commit 5446d17756
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
man/lvmsystemid.7.in
View File

@ -274,7 +274,7 @@ cache with pvscan --cache will allow a host to recognize the newly
exported VG. exported VG.
vgimport sets the VG system_id to the local system_id as determined by vgimport sets the VG system_id to the local system_id as determined by
lvm.conf system_id_sources. vgimport automatically scans storage for lvm.conf system_id_source. vgimport automatically scans storage for
newly exported VGs. newly exported VGs.
After vgimport, the exporting host will continue to see the VG as After vgimport, the exporting host will continue to see the VG as
@ -300,9 +300,9 @@ To move a VG from one host to another, vgexport and vgimport should be
used. used.
To forcibly gain ownership of a foreign VG, a host can add the foreign To forcibly gain ownership of a foreign VG, a host can add the foreign
system_id to its allow_system_id list, change the system_id of the foreign system_id to its extra_system_ids list, change the system_id of the
VG to its own, and remove the foreign system_id from its allow_system_id foreign VG to its own, and remove the foreign system_id from its
list. extra_system_ids list.
.SS shared VGs .SS shared VGs
@ -328,7 +328,7 @@ creation_host will be the same.
Orphan PVs are unused devices; they are not currently used in any VG. Orphan PVs are unused devices; they are not currently used in any VG.
Because of this, they are not protected by a system_id, and any host can Because of this, they are not protected by a system_id, and any host can
use them. Coodination of changes to orphan PVs is beyond the scope of use them. Coordination of changes to orphan PVs is beyond the scope of
system_id. The same is true of any block device that is not a PV. system_id. The same is true of any block device that is not a PV.
The effects of this are especially evident when lvm uses lvmetad caching. The effects of this are especially evident when lvm uses lvmetad caching.
@ -337,7 +337,7 @@ using the orphan, the other hosts will continue to report the PV as an
orphan. Nothing would automatically prevent the other hosts from using orphan. Nothing would automatically prevent the other hosts from using
the newly allocated PV and corrupting it. If the other hosts run a the newly allocated PV and corrupting it. If the other hosts run a
command to rescan devices, and update lvmetad, they would then recognize command to rescan devices, and update lvmetad, they would then recognize
the PV has been used by another host. A command that rescans devices that the PV has been used by another host. A command that rescans devices
could be pvscan --cache, or vgs --foreign. could be pvscan --cache, or vgs --foreign.
.SH SEE ALSO .SH SEE ALSO