|
|
Sponsored Content
Operating Systems
AIX
Having problems with removing a volume group..
Post 46148 by tommy on Friday 9th of January 2004 06:01:01 AM
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
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 REDHAT
vgdisplay
VGDISPLAY(8) System Manager's Manual VGDISPLAY(8) NAME
vgdisplay - display attributes of volume groups SYNOPSIS
vgdisplay [-A|--activevolumegroups] [-c|--colon] [-d|--debug] [-D|--disk] [-h|--help] [-s|--short] [-v[v]|--verbose [--verbose]] [--ver- sion] [VolumeGroupName...] DESCRIPTION
vgdisplay allows you to see the attributes of VolumeGroupName (or all volume groups if none is given) with it's physical and logical vol- umes and their sizes etc. OPTIONS -A, --activevolumegroups Only select the active volume groups. -c, --colon Generate colon seperated output for easier parsing in scripts or programs. The values are: 1 volume group name 2 volume group access 3 volume group status 4 internal volume group number 5 maximum number of logical volumes 6 current number of logical volumes 7 open count of all logical volumes in this volume group 8 maximum logical volume size 9 maximum number of physical volumes 10 current number of physical volumes 11 actual number of physical volumes 12 size of volume group in kilobytes 13 physical extent size 14 total number of physical extents for this volume group 15 allocated number of physical extents for this volume group 16 free number of physical extents for this volume group 17 uuid of volume group -d, --debug Enables additional debugging output (if compiled with DEBUG). -D, --disk Show attributes from the volume group descriptor area on disk(s). Without this switch they are shown from the kernel. Useful if the volume group isn't activated. -h, --help Print a usage message on standard output and exit successfully. -s, --short Give a short listing showing the existence of volume groups. -v, --verbose Display verbose information containing long listings of physical and logical volumes. If given twice, also display verbose runtime information of vgdisplay's activities. --version Display version and exit successfully. DIAGNOSTICS
vgdisplay returns an exit code of 0 for success and > 0 for error: 1 error reading VGDA 2 volume group doesn't exist 3 not all physical volumes of volume group online 4 volume group not found 5 no volume groups found at all 6 error reading VGDA from lvmtab 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 SEE ALSO
lvm(8), pvcreate(8), vgcreate(8), lvcreate(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS VGDISPLAY(8)