12-04-2006
Error on HACMP5.3 volume group on raw devices after exporting vg
Hello, johnf
No, in both cases, lsvg or lsvg -o VG is not visible and if we run lsvg -l vg01 we have 0516-306 error "Unable to find volume group vg01 in the Device Configuration Database"
Cristi
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
I'm new here, so this information may exist elsewhere on this forum. If so, please point me in the right direction.
Here's the problem.
I'm trying to migrate Oracle data from an HP system to a Sun system using a raw device as a 'bridge' between the two systems. Both machines... (4 Replies)
Discussion started by: Neville
4 Replies
2. 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
3. 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
4. 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
5. Programming
Hi guys.
what is the benefits of using raw devices in programming?
which applications mostly use raw devices?
how can i use raw devices in C programs? is there any system calls or library functions? (1 Reply)
Discussion started by: majid.merkava
1 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. 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
8. Red Hat
Can you please modify my script. This script is not working
for i in /dev/sdf
do
/bin/raw /dev/raw/`/bin/basename ${i}` ${i}
/bin/sleep 2
/bin/chown orasm:ordba /dev/raw/`/bin/basename ${i}`
/bin/chmod 660... (9 Replies)
Discussion started by: karthik9358
9 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. Solaris
Generally, this is what we do:-
On primary, export 2 LUNs (add-vdsdev).
On primary, assign these disks to the ldom in question (add-vdisk).
On ldom, created mirrored zpool from these two disks.
On one server (which is older) we have:-
On primary, create mirrored zpool from the two LUNs.... (4 Replies)
Discussion started by: psychocandy
4 Replies
LEARN ABOUT REDHAT
lvextend
LVEXTEND(8) System Manager's Manual LVEXTEND(8)
NAME
lvextend - extend the size of a logical volume
SYNOPSIS
lvextend [-A|--autobackup {y|n}] [-d|--debug] [-h|--help] {-l|--extents [+]LogicalExtentsNumber| -L|--size [+]LogicalVolumeSize[kKmMgGtT]}
[-v|--verbose] LogicalVolumePath [PhysicalVolumePath...]
DESCRIPTION
lvextend allows you to extend the size of a logical volume. Extension of snapshot logical volumes (see lvcreate(8) for information to cre-
ate snapshots) is supprted as well.
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.
-l, --extents [+]LogicalExtentsNumber
Extend or set the logical volume size in units of logical extents. With the + sign the value is added to the actual size of the
logical volume and without it, the value is taken as an absolute one.
-L, --size [+]LogicalVolumeSize[kKmMgGtT]
Extend or set the logical volume size in units in units of megabytes. A size suffix of M for megabytes, G for gigabytes or T for
terabytes is optional. With the + sign the value is added to the actual size of the logical volume and without it, the value is
taken as an absolute one.
-v, --verbose
Gives verbose runtime information about lvextend's activities.
Examples
"lvextend -L +54 /dev/vg01/lvol10 /dev/sdk3" tries to extend the size of that logical volume by 54MB on physical volume /dev/sdk3. This is
only possible if /dev/sdk3 is a member of volume group vg01 and there are enough free physical extents in it.
DIAGNOSTICS
lvextend returns an exit code of 0 for success or > 0 for error:
1 no logical volume name on command line
2 invalid physical volume name on command line
3 invalid logical volume name
4 error checking existence of logical volume
5 logical volume not active
6 error reading VGDA
7 requested physical volume not in this volume group
8 error getting index of logical volume
9 logical volume size not bigger than before
10 logical volume size exceeds volume group free capacity
11 logical volume size exceeds maximum
12 error setting up VGDA for logical volume extension
13 error extending VGDA for logical volume in kernel
14 error writing VGDA to physical volume(s)
15 error getting index for read/write statistics transfer
16 error getting status of logical volume from kernel
17 error setting up copy on write exception table
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).
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), lvcreate(8), lvreduce(8), lvchange(8)
AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com>
Heinz Mauelshagen LVM TOOLS LVEXTEND(8)