11-16-2009
AIX APPVG - QUORUM LOST, VOLUME GROUP CLOSING
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 cannot switch off quorum while the VG is not varied on - and I desperately need the VG up and running. Does anyone know how I can get my vg back up and running ?
Thank you and regards
zxmaus
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
Hi all,
I would like to ensure that a volume group has an effective quorum setting of 1 (or off). I know you can change the quorum setting using the chvg -Q command but want to know if the setting has been changed before the vg was varied on or a reboot.
In other words how can I ensure that... (3 Replies)
Discussion started by: backslash
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
Hi,
if I do install aix 5.3 on the rootvg of an aix 4.3.3 system (having rootvg and data1vg),
is it possible to varyonvg the data1vg after the installation ?
(any caution ?) (1 Reply)
Discussion started by: astjen
1 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. 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
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
9. AIX
Please let me know which volume group will be suitable for creation of 5 TB for datavg norma,big,scalable (4 Replies)
Discussion started by: manoj.solaris
4 Replies
10. AIX
I'm trying to change volume group of a disk, I'm setting up a PowerHa cluster and need to create a volume group named caavg_private and assigne it to hdisk3.
what is the right methods (commands) of doing this?
hdisk0 00f9a6dc66a06fcf None ... (1 Reply)
Discussion started by: spiderpig
1 Replies
LEARN ABOUT CENTOS
votequorum_qdevice_register
VOTEQUORUM_QDEVICE_REGISTER(3) Corosync Cluster Engine Programmer's Manual VOTEQUORUM_QDEVICE_REGISTER(3)
NAME
votequorum_qdevice_register - Registers a new quorum device
SYNOPSIS
#include <corosync/votequorum.h>
int votequorum_qdevice_register(votequorum_handle_t handle, const char * name);
DESCRIPTION
The votequorum_qdevice_register is used to register a new quorum device. A quorum device is an external way of adding votes to a small
cluster. The quorum device is, in effect, a pseudo node in the cluster that provide votes based on some external device, usually a shared
disk partition or perhaps a network router.
This call creates the device but does not mark it active. votequorum_qdevice_poll must be called for the votes to be included in the quo-
rum calculation.
name is string containing an informative name for the quorum device. It is simply stored by votequorum and used in the display of corosync-
quorumtool, it can be a maximum of 254 characters.
The number of votes contributed by the quorum device is already known to votequorum, it is set in cmap quorum.device.votes and not by the
device.
Note that it is the responsibility of the quorum device subsystem (not provided as part of votequorum) to keep all nodes informed of the
quorum device status.
RETURN VALUE
This call returns the CS_OK value if successful, otherwise an error is returned.
ERRORS
CS_ERR_TRY_AGAIN Resource temporarily unavailable
CS_ERR_INVALID_PARAM Invalid argument
CS_ERR_ACCESS Permission denied
CS_ERR_LIBRARY The connection failed
CS_ERR_INTERRUPT System call inturrupted by a signal
CS_ERR_NOT_SUPPORTED The requested protocol/functuality not supported
CS_ERR_MESSAGE_ERROR Incorrect auth message received
CS_ERR_NO_MEMORY Not enough memory to completed the requested task
SEE ALSO
votequorum_overview(8), votequorum_initialize(3), votequorum_finalize(3), votequorum_getinfo(3), votequorum_trackstart(3), votequo-
rum_trackstop(3), votequorum_fd_get(3), votequorum_dispatch(3), votequorum_context_set(3), votequorum_context_get(3), votequorum_setex-
pected(3), votequorum_setvotes(3), votequorum_qdevice_unregister(3), votequorum_qdevice_poll(3), votequorum_qdevice_update(3), votequo-
rum_qdevice_master_wins(3)
corosync Man Page 2014-06-10 VOTEQUORUM_QDEVICE_REGISTER(3)