exportvg


 
Thread Tools Search this Thread
Operating Systems AIX exportvg
# 8  
Old 11-28-2011
Do I hear several echoes?... Anyway.

Quote:
... through a command u can't check whether a VG is exported or not.
That's not true - if you simply issue a lsvg and your former VG isn't listed anymore, it must have been exported.
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. AIX

Exportvg/importvg causes corrupt LV Control Block

Hi experts, Power7 p720 AIX 6.1 This is what happened: $ sudo importvg -y v7000_1vg hdisk6 0516-622 synclvodm: Warning, cannot write lv control block data. 0516-622 synclvodm: Warning, cannot write lv control block data. 0516-622 synclvodm: Warning, cannot write lv control block data.... (9 Replies)
Discussion started by: livehho
9 Replies

2. AIX

nooB questions on importvg and exportvg

I don't understand the concept behind importvg and exportvg. What are some examples of when one would use this? (1 Reply)
Discussion started by: outtacontrol
1 Replies
Login or Register to Ask a Question
VGIMPORT(8)						      System Manager's Manual						       VGIMPORT(8)

NAME
vgimport - make exported volume groups known to the system SYNOPSIS
vgimport [-a|--all] [-d|--debug] [-h|-?|--help] [-v|--verbose] VolumeGroupName [VolumeGroupName...] DESCRIPTION
vgimport allows you to make a Volume Group that was previously exported using vgexport(8) known to the system again, perhaps after moving its Physical Volumes from a different machine. OPTIONS
See lvm(8) for common options. -a, --all Import all exported Volume Groups. --force Import exported Volume Groups even if there are missing Physical Volumes. This option should only be used if the missing devices are known to have failed and they cannot be restored. SEE ALSO
lvm(8), pvscan(8), vgexport(8), vgscan(8) Sistina Software UK LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) VGIMPORT(8)