The VG name is stored in the ODM, not on a disk. On the disk is only the VGDA which has the VGID stored.
You can use the following to read the VGDA before importing it:
It reads all information about the VGDA directly from the disk.
There is a part starting with "Logical:" which shows the LVs on this disk. The long number is the VGID, at least the part before the dot.
Why do you need to use the VG name from the former disk? To check the contents of the disk you could always import it with any name but a VG name that already exists.
hi guys..
I'm just wondering, everytime I go to a unix dictionary to get the definition of things such as $ and >& i dont get results back..
could you give me any link that has these simple definitions or could you tell me what $ means? or >&? (1 Reply)
I completely forgot this I am thinking of getting the book UNIX for dummies as a help to understand this class. Does anyone out there have this book? Is it helpful? (1 Reply)
on of the question that I have is that in class . We were asked this question
**What command would you use to list the last modification time of
all files in /tmp whose filenames end in exactly two digits?
I know that we need to to ls /tmp/ ??.... but I did not know how to find that last... (2 Replies)
Greetings,
I have a script that uses this syntax:
for i in `ls *.pll`
do
echo Compiling Lib $i .....
frmcmp.sh userid=$LOGON module_type=LIBRARY module=$i compile_all=yes batch=yes
done
mv *.pll ../libs
mv *.plx ../libs
mv *.err ../libs
If there are no files that match though I... (9 Replies)
Hello,
On Aix 5.3, during importvg, the varyonvg fails:
importvg -y vgtest hdisk20
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
When i use manually the command varyonvg -u -b -t vgtest to force, the vg can... (3 Replies)
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
LEARN ABOUT REDHAT
vgdisplay
VGDISPLAY(8) System Manager's Manual VGDISPLAY(8)NAME
vgdisplay - display attributes of volume groups
SYNOPSIS
vgdisplay [-A|--activevolumegroups] [-c|--colon] [-d|--debug] [-D|--disk] [-h|--help] [-s|--short] [-v[v]|--verbose [--verbose]] [--ver-
sion] [VolumeGroupName...]
DESCRIPTION
vgdisplay allows you to see the attributes of VolumeGroupName (or all volume groups if none is given) with it's physical and logical vol-
umes and their sizes etc.
OPTIONS
-A, --activevolumegroups
Only select the active volume groups.
-c, --colon
Generate colon seperated output for easier parsing in scripts or programs.
The values are:
1 volume group name
2 volume group access
3 volume group status
4 internal volume group number
5 maximum number of logical volumes
6 current number of logical volumes
7 open count of all logical volumes in this volume group
8 maximum logical volume size
9 maximum number of physical volumes
10 current number of physical volumes
11 actual number of physical volumes
12 size of volume group in kilobytes
13 physical extent size
14 total number of physical extents for this volume group
15 allocated number of physical extents for this volume group
16 free number of physical extents for this volume group
17 uuid of volume group
-d, --debug
Enables additional debugging output (if compiled with DEBUG).
-D, --disk
Show attributes from the volume group descriptor area on disk(s). Without this switch they are shown from the kernel. Useful if
the volume group isn't activated.
-h, --help
Print a usage message on standard output and exit successfully.
-s, --short
Give a short listing showing the existence of volume groups.
-v, --verbose
Display verbose information containing long listings of physical and logical volumes. If given twice, also display verbose runtime
information of vgdisplay's activities.
--version
Display version and exit successfully.
DIAGNOSTICS
vgdisplay returns an exit code of 0 for success and > 0 for error:
1 error reading VGDA
2 volume group doesn't exist
3 not all physical volumes of volume group online
4 volume group not found
5 no volume groups found at all
6 error reading VGDA from lvmtab
95 driver/module not in kernel
96 invalid I/O protocol version
97 error locking logical volume manager
98 invalid lvmtab (run vgscan(8))
99 invalid command line
SEE ALSO lvm(8), pvcreate(8), vgcreate(8), lvcreate(8)AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com>
Heinz Mauelshagen LVM TOOLS VGDISPLAY(8)