09-05-2015
Thanks for the input Hicksb8. I am doing this on my practice cluster luns are iscsi based.
I am just trying to implement the SCSI3 reservation on two path devices in cluster.
In first logs I just wanted to change the global_ default fencing to prefer3 mean scsi3 where it change all the reservation of shared disks from scsi2 to scsi3 except quorum device d6 which have I have to change it manually by adding d4 device as quorum (while adding this d4 device(Scsi3) in cluster, my command got hanged ). If my command didn't got hanged & went smoothly then remove the d6 from quorum device control then change the default_fencing parameter of device d6 to global from pathcount . After this I wanted to add the d6 in quorum device. & remove the d4 from quorum control. As in two node cluster we cannot directly remove the d6 (single)quorum device due to quorum of the server will be compromised untill & unless we put the cluster in installedmode which I did in seconds logs.
In both the above logs/procedure you will notice I am trying to add disk which is having scsi 3 reservation. Is due to adding the scsi3 reservation disk in quorum control my cluster got hanged both the times in above mention both logs meaning even simple "clq status" got hanged then I need to take the cluster reboot . As per my knowledge only these two process are to implement scsi3 reservation on two path devices.
My cluster is 3.2 & kindly let me know is their any way to implement scsi3 reservation on two path devices including quorum device.
Last edited by sb200; 09-05-2015 at 08:12 AM..
Reason: Wanted to add more information for clearity
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello agian !
What is the difference between SCSI and IDE hard disks ?
I have Intel PC and when i check i have Generic IDE TYPE DISK0
is IDE hard disk is ok for Solrais ? or should i buy the SCSI hard disk ?
Thanks
Abid Malik (3 Replies)
Discussion started by: abidmalik
3 Replies
2. AIX
Hi
Is it possible to install in p5 and pSeries SCSI Disks from SUN on DELL? Will they work?
Regards,
Pit (0 Replies)
Discussion started by: piooooter
0 Replies
3. Solaris
First time writer....take it easy on me.
I had a situation where I lost all paths to EMC disk. There was a failure on the EMC frame. After that was repaired, my server had a difficult time reclaiming all disks and veritas had marked the disks as failed. Veritas was confused. What are some of... (3 Replies)
Discussion started by: Sowser
3 Replies
4. Linux
Hi,
I am installing perl and rsnapshot on the OS of a Western Digital MyBook disk.
To install perl the ./Configure command tells me that both 'tr' and 'split' are missing. I don't find them on the net.
Where can I download them?
Thanks.
Charles. (2 Replies)
Discussion started by: mosndup
2 Replies
5. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
6. Solaris
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
7. Solaris
Hi All,
I am a RH Linux admin that recently started working at a company with a number of SUN Servers so it's been an interesting transition.
Considering the last person left with very little documentation left behind so I have been picking up most issues half complete, or troubleshot.
... (7 Replies)
Discussion started by: MobileGSP
7 Replies
8. HP-UX
Hi guys,
I need some help to better understand how to determine if a disk have persistent SCSI reservation. I know that we should use the "Persisten Reservation Utility" but we are not allowed to run that tool. Since we have the output from some grab utility and specifically we have the... (0 Replies)
Discussion started by: cecco16
0 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)