09-24-2007
I still can't get this question. Why would you worry about "quorum" on an active VG ?.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Did anyone knows how to check size/usage of a Volume Group in AIX 4.3.3? (4 Replies)
Discussion started by: s_aamir
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. Emergency UNIX and Linux Support
Hi,
I am running AIX 5.3 TL8. After a disk failure, one of my mirrored application volumegroups went down. Unfortunately we have quorum switched on on this VG and the defective disk holds the majority.
I have set MISSINGPV_VARYON to TRUE and tried a forced varyon but it's still failing. I... (3 Replies)
Discussion started by: zxmaus
3 Replies
5. 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
6. Red Hat
Hello,
How can I obtain a lists of disks with their size (anytype: SAN LUNs, internal disks, etc.) attached to the system and not being extended inside a volume group?
The purpose of this list is to be part of a function of a script that I'm doing in order to resize filesystems and in the... (6 Replies)
Discussion started by: asanchez
6 Replies
7. 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
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. AIX
Hi huys,
Sorry for my bad english, i'm french :o .
I've got a little question : is there a way to check status of a VG on aix 6.1 ? I want to know if a VG is locked or not...
I can do a "lsvg -Ll rootvg" for example, but if this VG is already locked, the process waits without gives me the... (2 Replies)
Discussion started by: akorx
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 DEBIAN
mkqdisk
mkqdisk(8) Quorum Disk Management mkqdisk(8)
NAME
mkqdisk - Cluster Quorum Disk Utility
WARNING
Use of this command can cause the cluster to malfunction.
SYNOPSIS
mkqdisk [-?|-h] | [-L] | [-f label] [-c device -l label] [-d [-d ...]]
DESCRIPTION
The mkqdisk command is used to create a new quorum disk or display existing quorum disks accessible from a given cluster node.
OPTIONS
-c device -l label
Initialize a new cluster quorum disk. This will destroy all data on the given device. If a cluster is currently using that device
as a quorum disk, the entire cluster will malfunction. Do not run this on an active cluster when qdiskd is running. Only one
device on the SAN should ever have the given label; using multiple different devices is currently not supported (it is expected a
RAID array is used for quorum disk redundancy). The label can be any textual string up to 127 characters - and is therefore enough
space to hold a UUID created with uuidgen(1).
-f label
Find the cluster quorum disk with the given label and display information about it.
-L Display information on all accessible cluster quorum disks.
-d Increase debugging level. Specify multiple times for more information. Currently, specifying more than twice has no effect.
SEE ALSO
qdisk(5), qdiskd(8), uuidgen(1)
July 2006 mkqdisk(8)