12-04-2006
I trust that if you run lsvg on the failover node the VG is visible and if you run lsvg -o it is not.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
I'm new here, so this information may exist elsewhere on this forum. If so, please point me in the right direction.
Here's the problem.
I'm trying to migrate Oracle data from an HP system to a Sun system using a raw device as a 'bridge' between the two systems. Both machines... (4 Replies)
Discussion started by: Neville
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. 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. Programming
Hi guys.
what is the benefits of using raw devices in programming?
which applications mostly use raw devices?
how can i use raw devices in C programs? is there any system calls or library functions? (1 Reply)
Discussion started by: majid.merkava
1 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
Can you please modify my script. This script is not working
for i in /dev/sdf
do
/bin/raw /dev/raw/`/bin/basename ${i}` ${i}
/bin/sleep 2
/bin/chown orasm:ordba /dev/raw/`/bin/basename ${i}`
/bin/chmod 660... (9 Replies)
Discussion started by: karthik9358
9 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. Solaris
Generally, this is what we do:-
On primary, export 2 LUNs (add-vdsdev).
On primary, assign these disks to the ldom in question (add-vdisk).
On ldom, created mirrored zpool from these two disks.
On one server (which is older) we have:-
On primary, create mirrored zpool from the two LUNs.... (4 Replies)
Discussion started by: psychocandy
4 Replies
LEARN ABOUT SUSE
crm_failcount
CRM_FAILCOUNT(8) [FIXME: manual] CRM_FAILCOUNT(8)
NAME
crm_failcount - manipulate the failcount attribute on a given resource
SYNOPSIS
crm_failcount [-?|-V] -D -u|-U node -r resource
crm_failcount [-?|-V] -G -u|-U node -r resource
crm_failcount [-?|-V] -v string -u|-U node -r resource
DESCRIPTION
Heartbeat implements a sophisticated method to compute and force failover of a resource to another node in case that resource tends to fail
on the current node. A resource carries a resource_stickiness attribute to determine how much it prefers to run on a certain node. It also
carries a resource_failure_stickiness that determines the threshold at which the resource should failover to another node.
The failcount attribute is added to the resource and increased on resource monitoring failure. The value of failcount multiplied by the
value of resource_failure_stickiness determines the failover score of this resource. If this number exceeds the preference set for this
resource, the resource is moved to another node and not run again on the original node until the failure count is reset.
The crm_failcount command queries the number of failures per resource on a given node. This tool can also be used to reset the failcount,
allowing the resource to run again on nodes where it had failed too often.
OPTIONS
--help, -?
Print a help message.
--verbose, -V
Turn on debug information.
Note
Increase the level of verbosity by providing additional instances.
--quiet, -Q
When doing an attribute query using -G, print just the value to stdout. Use this option with -G.
--get-value, -G
Retrieve rather than set the preference.
--delete-attr, -D
Specify the attribute to delete.
--attr-value string, -v string
Specify the value to use. This option is ignored when used with -G.
--node-uuid node_uuid, -u node_uuid
Specify the UUID of the node to change.
--node-uname node_uname, -U node_uname
Specify the uname of the node to change.
--resource-id resource name, -r resource name
Specify the name of the resource on which to operate.
EXAMPLES
Reset the failcount for the resource myrsc on the node node1:
crm_failcount -D -U node1 -r my_rsc
Query the current failcount for the resource myrsc on the node node1:
crm_failcount -G -U node1 -r my_rsc
FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.
SEE ALSO
???, ???, and the Linux High Availability FAQ Web site[1]
AUTHOR
crm_failcount was written by Andrew Beekhof.
NOTES
1. Linux High Availability FAQ Web site
http://www.linux-ha.org/v2/faq/forced_failover
[FIXME: source] 07/05/2010 CRM_FAILCOUNT(8)