04-12-2016
It makes no sense to create anything else than scalable VGs any more.
On the downside scalable VGs cannot be used in AIX versions prior to 5.3. Should you need to move the VG between such an (already completely) unsupported system and the AIX 6.1 LPAR you are the exception to this rule.
On the upside: everything else. The minimally slower operation of some of the VG-manipulating commands set aside (you probably will not even notice the difference) set aside scalable VG are more flexible, more easily extendable and offer more maximum space.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB.
If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information
Regards
Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies
2. AIX
Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies
3. AIX
Hi,
if I do install aix 5.3 on the rootvg of an aix 4.3.3 system (having rootvg and data1vg),
is it possible to varyonvg the data1vg after the installation ?
(any caution ?) (1 Reply)
Discussion started by: astjen
1 Replies
4. Emergency UNIX and Linux Support
Hi,
I am running AIX 5.3 TL8. After a disk failure, one of my mirrored application volumegroups went down. Unfortunately we have quorum switched on on this VG and the defective disk holds the majority.
I have set MISSINGPV_VARYON to TRUE and tried a forced varyon but it's still failing. I... (3 Replies)
Discussion started by: zxmaus
3 Replies
5. AIX
Hello,
I am a french computer technician, and i speak English just a little.
On Aix 5.3, I encounter a name conflict logical volume on two volume group.
The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM
root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies
6. AIX
Hi,
I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over)
Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes... (6 Replies)
Discussion started by: aixromeo
6 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies
1)Physical Volume
2)Volume Group
3)Logical Volume
4)Physical Partition
Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies
8. UNIX for Dummies Questions & Answers
hi,
I want to create a volume group of 200 GB and then create different file systems on that.
please help me out. Its becomes confusing when the PP calculating PP.
I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies
9. Red Hat
Hello Guys,
I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var.
I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
10. AIX
I'm trying to change volume group of a disk, I'm setting up a PowerHa cluster and need to create a volume group named caavg_private and assigne it to hdisk3.
what is the right methods (commands) of doing this?
hdisk0 00f9a6dc66a06fcf None ... (1 Reply)
Discussion started by: spiderpig
1 Replies
LEARN ABOUT DEBIAN
vgrename
VGRENAME(8) System Manager's Manual VGRENAME(8)
NAME
vgrename - rename a volume group
SYNOPSIS
vgrename [-A|--autobackup y|n] [-d|--debug] [-h|-?|--help] [-t|--test] [-v|--verbose] OldVolumeGroup{Path|Name|UUID} NewVol-
umeGroup{Path|Name}
DESCRIPTION
vgrename renames an existing (see vgcreate(8) ) volume group from OldVolumeGroup{Name|Path|UUID} to NewVolumeGroup{Name|Path}.
OPTIONS
See lvm for common options.
Examples
"vgrename /dev/vg02 /dev/my_volume_group" renames existing volume group "vg02" to "my_volume_group".
"vgrename vg02 my_volume_group" does the same.
"vgrename Zvlifi-Ep3t-e0Ng-U42h-o0ye-KHu1-nl7Ns4 VolGroup00_tmp"
changes the name of the Volume Group with UUID Zvlifi-Ep3t-e0Ng-U42h-o0ye-KHu1-nl7Ns4 to "VolGroup00_tmp".
All the Volume Groups visible to a system need to have different names. Otherwise many LVM2 commands will refuse to run or give
warning messages.
This situation could arise when disks are moved between machines. If a disk is connected and it contains a Volume Group with the
same name as the Volume Group containing your root filesystem the machine might not even boot correctly. However, the two Volume
Groups should have different UUIDs (unless the disk was cloned) so you can rename one of the conflicting Volume Groups with
vgrename.
SEE ALSO
lvm(8), vgchange(8), vgcreate(8), lvrename(8)
Sistina Software UK LVM TOOLS 2.02.95(2) (2012-03-06) VGRENAME(8)