LVM Breaking the Persistent Reserve: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== Breaking the Persistent Reserve of a Shared Non-concurrent Volume Group === # Special care must be taken when using this method of importing changes of a shared volume grou...") |
No edit summary |
||
Line 1: | Line 1: | ||
== Breaking the Persistent Reserve of a Shared Non-concurrent Volume Group | == Breaking the Persistent Reserve of a Shared Non-concurrent Volume Group == | ||
# Special care must be taken when using this method of importing changes of a shared volume group. The system can become corrupted and data loss will occure. | # Special care must be taken when using this method of importing changes of a shared volume group. The system can become corrupted and data loss will occure. | ||
# On the system with the online active volume group, break the persistent reserve. | # On the system with the online active volume group, break the persistent reserve. |
Latest revision as of 17:10, 8 August 2014
- Special care must be taken when using this method of importing changes of a shared volume group. The system can become corrupted and data loss will occure.
- On the system with the online active volume group, break the persistent reserve.
- # varyonvg -bu <volume group>
- On the system you want to import the changes to, import the volume group but DO NOT activate it.
- # importvg -L <volume group> -n <physical volume>
- After the import is successful on the online active volume group, reset the persistent reserve.
- # varyonvg <volume group>