01-09-2004
Uh.. quite hard one you throw to me.
Could you please provide me some more information:
Outputs of "varyonvg <vgname>", "lsvg -p <vgname>", "lsdev -Cc disk | grep hdisk3", "lspv | grep <vgname>" and "lqueryvg -Atp hdisk3" might help me to get on right track with this one.
--Tommy
10 More Discussions You Might Find Interesting
1. AIX
Looking for help in understanding volume groups.
On the internal disks is it possible to have other volume groups other then root vg? If so would the other vg be captured in the mksysb?
Any documentation links that you can point me to on volume groups and such woudl be welcomed.
Thanks (1 Reply)
Discussion started by: cogsworth12000
1 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. 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
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. Red Hat
Our SAN administrator decided to unpresent then destroy LUN's we were actively using as a volume group (all PV's in said volume group). Now every time I do a pvscan or whatever it complains about I/O errors trying to access those PV's. How do I get it to forget the VG existed completely? vgreduce... (7 Replies)
Discussion started by: thmnetwork
7 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 want to remove hdisk1 from volume group diskpool_4 and migrate PV from hdisk1 to hdisk2 , but facing problems, so what is the quickest way to migratepv and remove hdisk1 --
# lspv | grep diskpool_4
hdisk1 00c7780e2e21ec86 diskpool_4 active
hdisk2 ... (2 Replies)
Discussion started by: filosophizer
2 Replies
LEARN ABOUT HPUX
vgexport
vgexport(1M) vgexport(1M)
NAME
vgexport - export an LVM volume group and its associated logical volumes
SYNOPSIS
mapfile] outfile] vg_name
mapfile vg_name
DESCRIPTION
Using the format of the first command line of the above, the command can be used to remove a volume group from the system. The volume
group will be removed without modifying the logical volume information found on the physical volumes.
The volume group identified by vg_name is removed from the or file, and the associated device files including the vg_name directory and
file are removed from the system.
The volume group information and data is untouched on the physical volume. These disks can be imported to another system with the command
(see vgimport(1M)).
Scan Option
Using the format of the second command line of the above, the command generates a mapfile that can be copied to other systems that are part
of a high availability cluster (use the option if you do not want to remove the volume group from the system the command is being run from)
and the command (see vgimport(1M)) can be used to recreate the volume group. See also vgchange(1M). The mapfile contains a description of
the volume group and its associated logical volume(s) (if any). The logical volume information found on the physical volumes is not modi-
fied.
Options and Arguments
recognizes the following options and arguments:
vg_name The path name of the volume group.
By default, a file named
is created in the current directory. This file contains a description of the volume group and its associated logical
volume(s) (if any). Use this option to specify a different name for the file, mapfile. This file can be used as
input to (see vgimport(1M)). When used with the option, the volume group specified in the mapfile can be shared with
other systems in the high availability cluster.
Preview the actions to be taken but do not update the
or file or remove the devices file. This option is best used in conjunction with the option.
Print verbose messages
including the names of the physical volumes associated with this volume group.
Scan option. When the option is specified, then the options must also be specified. A mapfile is created that can be used to cre-
ate volume group entries on other systems in the high availability cluster (with the command).
Write the current set of
pv_paths for the volume group to the outfile. The outfile may then be used as the infile for the option. If used
together with the option the volume group is not exported but the list of pv_paths is still written to the outfile.
This may be useful to derive a list of pv_paths for the volume group or to use on another system which is sharing the
volume group and which has an identical configuration.
EXTERNAL INFLUENCES
Environment Variables
determines the language in which messages are displayed.
If is not specified or is null, it defaults to "C" (see lang(5)).
If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)).
EXAMPLES
Export the volume group into mapfile The volume group will be removed from the exporting system.
Export the volume group and write the disk names into the file
Create a mapfile to be copied to other systems in a high availability cluster to build the volume group information for the volume group,
Note that the volume group is not removed from the exporting system. The importing systems will create the volume group with the command
using the and options.
SEE ALSO
vgimport(1M), vgscan(1M).
vgexport(1M)