07-14-2002
Logical Volume Manager question
After creating a make recover tape on a TAC-4 9000/770, the system lost three of five volume groups from the /etc/lvmtab. What would be the best way to recreate the volume groups in the lvmtab?
7 More Discussions You Might Find Interesting
1. AIX
Hi All,
There is AIX server which has 2 internal disks running the OS and 8 external disks on a RAID array with RAID 5. My question - is there a way to check which are the logical volumes and file system configured on this RAID array (2 Replies)
Discussion started by: rramanuj
2 Replies
2. AIX
I have a pretty basic question but I am finding my self stumped...
I am trying to find the config that shows which logical volume is mapped to which physical volume
IE:
I know that pdisk15 is mapped to hdisk17 (I only know this as it was told to me though, by IBM)
When I run: lslv -p... (5 Replies)
Discussion started by: pheusion
5 Replies
3. 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
4. AIX
Hi!
Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes?
What items should I check, like where do I look at in smit? Or are there commands that I should execute?
I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies
5. Solaris
What are the comman line instructions need to be used to know if a Logical Volume Manager is installed on solaris Box, What is its name, version, driver version, library version. (1 Reply)
Discussion started by: epriya2003
1 Replies
6. UNIX for Advanced & Expert Users
I am trying to build a veritas volume similar to an existing volume on another server. The output on source server is:
usbtor12# vxprint -hrtg appdg
v anvil_sqlVOL - ENABLED ACTIVE 629145600 SELECT - fsgen
pl anvil_sqlVOL-01 anvil_sqlVOL ENABLED ACTIVE 629145600... (3 Replies)
Discussion started by: momin313
3 Replies
7. 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
LEARN ABOUT REDHAT
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] [-v|--verbose] { OldVolumeGroupPath NewVolumeGroupPath | OldVolumeName NewVol-
umeGroupName }
DESCRIPTION
vgrename renames an existing (see vgcreate(8) ) volume group.
OPTIONS
-A, --autobackup y/n
Controls automatic backup of VG metadata after the change ( see vgcfgbackup(8) ). Default is yes.
-d, --debug
Enables additional debugging output (if compiled with DEBUG).
-h, --help
Print a usage message on standard output and exit successfully.
-v, --verbose
Gives verbose information about vgrename's activities.
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.
DIAGNOSTICS
vgrename returns an exit code of 0 for success and > 0 for error:
1 new volume group directory for device special files already exists
2 old volume group directory for device special files doesn't exist
3 new volume group name is invalid
4 old volume group name is invalid
5 error checking existence of old volume group
7 volume group names are identical
8 new volume group already exists
9 error reading VGDA
10 error removing old VGDA from kernel
11 error removing old VGDA from lvmtab
12 error removing device special files for old volume group
13 error creating device special files for new volume group
14 error inserting new volume group name into lvmtab
15 error backinp up VGDA
16 error writing VGDA to lvmtab
17 error renaming volume group in kernel
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
ENVIRONMENT VARIABLES
LVM_AUTOBACKUP
If this variable is set to "no" then the automatic backup of VG metadata is turned off.
LVM_VG_MAX_BACKUPS
This variable determines the backup history depth of kept VGDA copy files in /etc/lvmconf. It can be set to a positive number
between 0 and 999. The higher this number is, the more changes you can restore using vgcfgrestore(8).
See also
lvm(8), vgchange(8), vgcreate(8), lvrename(8)
AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com>
Heinz Mauelshagen LVM TOOLS VGRENAME(8)