LVM Breaking the Persistent Reserve: Difference between revisions

From UNIX Systems Administration
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...")
 
 
(One intermediate revision by the same user not shown)
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.
## <tt>'''# varyonvg -bu <volume group>'''</tt>
#: <tt>'''# varyonvg -bu <volume group>'''</tt>
# On the system you want to import the changes to, import the volume group but <b>DO NOT</b> activate it.
# On the system you want to import the changes to, import the volume group but <b>DO NOT</b> activate it.
## <tt>'''# importvg -L <volume group> -n <physical volume>'''</tt>
#: <tt>'''# importvg -L <volume group> -n <physical volume>'''</tt>
# After the import is successful on the online active volume group, reset the persistent reserve.
# After the import is successful on the online active volume group, reset the persistent reserve.
## <tt>'''# varyonvg <volume group>'''</tt>
#: <tt>'''# varyonvg <volume group>'''</tt>


== Further Reading ==
== Further Reading ==

Latest revision as of 19:39, 2 April 2026

Breaking the Persistent Reserve of a Shared Non-concurrent Volume Group

  1. 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.
  2. On the system with the online active volume group, break the persistent reserve.
    # varyonvg -bu <volume group>
  3. 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>
  4. After the import is successful on the online active volume group, reset the persistent reserve.
    # varyonvg <volume group>

Further Reading

  1. Non-Concurrent Shared Volume Changes