Sponsored Content
Operating Systems AIX AIX procedure for creating a logical volume from CLI Post 302141706 by bakunin on Monday 22nd of October 2007 03:25:23 AM
Old 10-22-2007
The problem may be that the hdisk (which seems to come from some storage subsystem) is already in use on another system. The system will discover the PVID and the VG-information only after establishing access to the disk, which isn't possible as long as it is used by another system concurrently.

bakunin
 

10 More Discussions You Might Find Interesting

1. AIX

AIX Logical Volume Question

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. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

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

3. AIX

Moving a Logical Volume from one Volume Group to Another

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

4. AIX

Basic Filesystem / Physical Volume / Logical Volume Check

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. AIX

Logical volume name conflict in two volume group

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. Solaris

CLI to get info for Logical Volume manager

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

7. HP-UX

Creating a logical volume file

Hi to all, I am brand new to HP-UX but am quite familiar with Linux systems (Red Hat, Ubuntu etc..) I've just taken over a new HP-UX box and trying to work out how to create a logical volume. As well as creating the volume, which I am sure is very easy I need to create a special character... (6 Replies)
Discussion started by: jamie2teach
6 Replies

8. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

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

9. AIX

Position of the logical volume on the physical volume

Hello everyone, I just read that while creating a logical volume(LV) we can choose the region of the physical volume (PV) in which the LV should be created. When I say region I mean: outer edge - outer middle - center - inner middle and inner edge. Can anyone help me understand the utility... (11 Replies)
Discussion started by: adilyos
11 Replies

10. Red Hat

No space in volume group. How to create a file system using existing logical volume

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
LVRENAME(8)						      System Manager's Manual						       LVRENAME(8)

NAME
lvrename - rename a logical volume SYNOPSIS
lvrename [-A|--autobackup {y|n}] [-d|--debug] [-h|--help] [-v|--verbose] [--version] {OldLogicalVolumePath NewLogicalVolume{Path|Name} | VolumeGroupName OldLogicalVolumeName NewLogicalVolumeName} DESCRIPTION
lvrename renames an existing logical volume from OldLogicalVolume{Name|Path} to NewLogicalVolume{Name|Path}. 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 progress messages. EXAMPLE
To rename lvold in volume group vg02 to lvnew: lvrename /dev/vg02/lvold /dev/vg02/lvnew An alternate syntax to rename this logical volume is lvrename vg02 lvold lvnew DIAGNOSTICS
lvrename returns an exit code of 0 for success or > 0 for error: 1 invalid logical volume name 2 error checking existence of volume group 3 volume group inactive 4 new logical volume special file already exists 5 old logical volume doesn't exist 6 volume group names are different 7 new logical volume already exist 9 error reading volume group 10 error getting index of old logical volume 11 error renaming logical volume in kernel 12 error creating new logical volume in kernel 13 error writing VGDA to physical volume(s) 14 error creating device special for new logical volume 15 invalid volume group name 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 determins 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 steps are you able to backup with vgcfgrestore(8) from the changes you make to your volume groups. LVM_VG_NAME The default Volume Group Name to use. Setting this variable enables you to enter just the Logical Volume Name rather than its com- plete path. SEE ALSO
lvm(8), lvchange(8), vgcreate(8), vgrename(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS LVRENAME(8)
All times are GMT -4. The time now is 03:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy