12-05-2009
both copies reported by the command lslv are on the physical volume of rootvg: hdisk0 and hdisk1.
Both copies will not affect the datavg vg.
In fact I try to delete, without impacting applications, the problem of name conflict logical volume on this server. There are two times the logical volume lvnode01 : once in the volume group rootvg (mounted and active) and a second time in another volume group datavg (unmounted, not in the ODM but present in VGDA off physical volume related volume group datavg).
After some research I think the command synclvodm could solve the problem of name conflict by renaming the logical volume automatically by default.
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. HP-UX
Hi all,
How do u rename a logical volume group and the logical volumes belonging to that? The logical volumes contain data and are in use.
eg: Renaming dev/vgov to dev/ov-dg ? (6 Replies)
Discussion started by: Mr. Zer0
6 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. HP-UX
Hi,
Someone please help me with how i can unmount and remove all the files systems from a cluster. This is being shared by two servers that are active_standby. (3 Replies)
Discussion started by: joeli
3 Replies
6. 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
7. AIX
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
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. Ubuntu
Hello,
I'm running Ubuntu 12.04. I need to rename my root logical volume group and it's bootmanager/fstab accordingly.
Here is the output: I need to change the HP-TEST001 to PRODGROUP01. Please advice me.
root@PROD-02:/home# vgdisplay
--- Volume group ---
VG Name HP-TEST001
System ID... (2 Replies)
Discussion started by: moneynut
2 Replies
10. 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
vgimport
VGIMPORT(8) System Manager's Manual VGIMPORT(8)
NAME
vgimport - make volume groups known to the system
SYNOPSIS
vgimport [-d|--debug] [-f|--force] [-h|--help] [-v|--verbose] VolumeGroupName PhysicalVolumePath [PhysicalVolumePath...]
DESCRIPTION
vgimport allows you to make a volume group known to the system which has previously been exported (see vgexport(8) ) on this or another
system.
OPTIONS
-d, --debug
Enables additional debugging output (if compiled with DEBUG).
-f, --force
Force import of volume group even though it is not flagged exported. This option allows the importing of volume groups from broken
systems.
-h, --help
Print a usage message on standard output and exit successfully.
-v, --verbose
Display verbose runtime information about vgimport's activities.
Examples
"vgimport myvg /dev/sd[b-h]5" tries to make new volume group "myvg" known to the system. The previously exported volume group (see vgex-
port(8) ) resides on disk partitions "/dev/sdb5" to "/dev/sdh5".
DIAGNOSTICS
vgimport returns an exit code of 0 for success and > 0 for error:
1 no volume group name on command line
2 invalid volume group name
3 no physical volume(s) on command line
4 volume group already exists
5 physical volume occurs mutiple times on command line
6 invalid physical volume name
7 error reading physical volume
8 physical volume is not exported
9 error reallocating memory
10 error allocating memory
11 no valid physical volumes found
12 physical volume belongs to a different exported volume group
13 wrong number of physical volumes
14 error reading VGDA from disk(s)
15 VGDA is inconsistent
16 invalid logical volume count
17 error getting a free volume group number
18 error writing VGDA to physical volumes
19 error creating VGDA in kernel
20 error inserting volume group into lvmtab
21 error doing backup of VGDA to disk
22 error storing VGDA in lvmtab
23 not enough free logical volume manager block specials available
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
Example
"vgimport this_import /dev/sdk3 /dev/sdj4" tries to import a volume group contained on both partitions. The volume group this_import may
not already exit. You have to specify all physical volumes belonging to the exported volume group.
See also
lvm(8), lvcreate(8)
AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com>
Heinz Mauelshagen LVM TOOLS VGIMPORT(8)