10-31-2008
Quote:
And not the other packages?
??
Is this VG a new VG? and you forgot to add in your <packagename>.cfg file ?
The other packages do not have VG's assigned to them, only this one.
It is a new VG, and it has been added to the packagename.cfg file.
The VG comes from SAN disks that are presented to both nodes. Everything works fine, except for the fact that a manual vg activation has to occur any time we move the package from one node to the other.
10 More Discussions You Might Find Interesting
1. HP-UX
Excuse the basic nature of the question, I've zero experience with regards to this and I'm just looking for a little clarity...
When using serviceguard for a failover from one machine to another, what doesn't get taken from one machine to the other? For example, I was told that OS users and... (1 Reply)
Discussion started by: stefcha
1 Replies
2. High Performance Computing
I have rcently setup a 4 node cluster running sun cluster 3.2
and I have installed 4 zones on each node. when installing the zones I had to install the zone on all nodes the on the last node do a zlogin -C <zonename>
this worked ok.
theni I tried to siwitch the zone to node a thei work... (14 Replies)
Discussion started by: lesliek
14 Replies
3. HP-UX
Hi, I'm fairly new to HP-UX. I am trying to find out if it is possible to create a cluster with 3 active nodes and 1 passive node. Everything I have found online so far just describes active/active and active/passive.
Is it possible to have 3 active nodes and 1 passive node in a cluster? If... (2 Replies)
Discussion started by: DtbCollumb
2 Replies
4. AIX
Dear All,
I would like to ask about saving & restoring a user defined volume group. i have a user defined volume group, named as datavg. i want to save it & to restore it into different size of physical volume. currently, datavg consist of 4 pv, three fisrt pv size are 100GB & one pv size is... (1 Reply)
Discussion started by: donybangetgitu
1 Replies
5. Solaris
Hi,
We have two sun SPARC server in Clustered (Sun Cluster 3.1). For some reason, System 1 failed over to System 2. Where can I find the logs which could tell me the reason for this failover?
Thanks (5 Replies)
Discussion started by: Mack1982
5 Replies
6. Gentoo
How to failover the cluster ? GNU/Linux
By which command,
My Linux version
2008 x86_64 x86_64 x86_64 GNU/Linux
What are the prerequisites we need to take while failover ?
if any
Regards (3 Replies)
Discussion started by: sidharthmellam
3 Replies
7. 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
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. Linux
Hey! I'm running a HP ServiceGuard cluster with three nodes. One of the packages was moved (not by me) from one node to another a few weeks ago.
I just noticed that one of the volume groups is still mounted on the old node. Oops! When I run df, less space is used on the old node than the new.
... (0 Replies)
Discussion started by: tobiasvl
0 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 CENTOS
ocf_heartbeat_lvm
OCF_HEARTBEAT_LVM(7) OCF resource agents OCF_HEARTBEAT_LVM(7)
NAME
ocf_heartbeat_LVM - Controls the availability of an LVM Volume Group
SYNOPSIS
LVM [start | stop | status | monitor | meta-data | validate-all]
DESCRIPTION
Resource script for LVM. It manages an Linux Volume Manager volume (LVM) as an HA resource.
SUPPORTED PARAMETERS
volgrpname
The name of volume group.
(required, string, no default)
exclusive
If set, the volume group will be activated exclusively. This option works one of two ways. If the volume group has the cluster
attribute set, then the volume group will be activated exclusively using clvmd across the cluster. If the cluster attribute is not set,
the volume group will be activated exclusively through the use of the volume_list filter in lvm.conf. In the filter scenario, the LVM
agent verifies that pacemaker's configuration will result in the volume group only being active on a single node in the cluster and
that the local node's volume_list filter will prevent the volume group from activating outside of the resource agent. On activation
this agent claims the volume group through the use of a unique tag, and then overrides the volume_list field in a way that allows the
volume group to be activated only by the agent. To use exclusive activation without clvmd, the volume_list in lvm.conf must be
initialized. If volume groups exist locally that are not controlled by the cluster, such as the root volume group, make sure those
volume groups are listed in the volume_list so they will be allowed to activate on bootup.
(optional, boolean, default false)
tag
If "exclusive" is set on a non clustered volume group, this overrides the tag to be used.
(optional, string, default "pacemaker")
partial_activation
If set, the volume group will be activated even only partial of the physical volumes available. It helps to set to true, when you are
using mirroring logical volumes.
(optional, string, default "false")
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 30.
stop
Stops the resource. Suggested minimum timeout: 30.
status
Performs a status check. Suggested minimum timeout: 30.
monitor
Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10.
methods
Suggested minimum timeout: 5.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a LVM resource using the crm(8) shell:
primitive p_LVM ocf:heartbeat:LVM
params
volgrpname=string
op monitor depth="0" timeout="30" interval="10"
SEE ALSO
http://www.linux-ha.org/wiki/LVM_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_LVM(7)