12-23-2019
Hi Neo and rbattel
my system are using GPFS(archive directory) and raw devices with Oracle RAC on the hacmp.
I think the reason why A-system has down itself is that B-system is down due to system bug and all oracle sessions of B-system node are moved to A-system, which causes huge IO on A-system. The sync time of the A-system was slowed down, and as a result, the system was down when the dead man switch limit was reached.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. HP-UX
hi friends,
i know that when there is a crash then that memory image is
put into /var/adm/crash
but if the system hangs up and if i have access to console of
that machine then how can i take the crash dump manully.
thanks (2 Replies)
Discussion started by: mxms755
2 Replies
3. Solaris
Can anyone of you help me in enabling crash dump on Solaris 5.5.1 (1 Reply)
Discussion started by: csreenivas
1 Replies
4. AIX
Hi Guys,
I have two nodes clustered. Each node is AIX 5.2 & they are clustered with HACMP 5.2. The mode of the cluster is Active/Passive which mean one node is the Active node & have all resource groups on it & the 2nd node is standby.
Last Monday I noted that all resource groupes have been... (2 Replies)
Discussion started by: aldowsary
2 Replies
5. Solaris
hi ,
i have machine that is crashed
how i can enable core dump file & how can i find it ? :confused: (4 Replies)
Discussion started by: lid-j-one
4 Replies
6. UNIX for Advanced & Expert Users
Hi.
I have started heartbeat on two redhat servers. Using eth0.
Before I start heartbeat I can ping the two server to each other.
Once I start heartbeat both the server become active as they both have warnings that the other node is dead.
Also I am not able to ping each other. After stopping... (1 Reply)
Discussion started by: amrita garg
1 Replies
7. AIX
Hi Guys,
I have to design a multinode hacmp cluster and am not sure if the design I am thinking of makes any sense.
I have to make an environment that currently resides on 5 nodes more resilient but I have the constrain of only having 4 frames. In addition the business doesnt want to pay for... (7 Replies)
Discussion started by: zxmaus
7 Replies
8. AIX
Hi
I had an active passive cluster. Node A went down and all resource groups moved to Node B.
Now we brought up Node A. What is the procedure to bring everything back to Node A.
Node A #lssrc -a | grep cl
clcomdES clcomdES 323782 active
clstrmgrES cluster... (9 Replies)
Discussion started by: samsungsamsung
9 Replies
9. HP-UX
Hi Experts,
I have configured HP-UX Service Guard cluster and it dumps crash every time i reboot a cluster node. Can anyone please help me to prevent these unnecessary crash dumps at the time of rebooting SG cluster node?
Thanks in advance.
Vaishey (2 Replies)
Discussion started by: Vaishey
2 Replies
10. OS X (Apple)
MacPro (2013) 12-Core, 64GB RAM (today's crash):
panic(cpu 2 caller 0xffffff7f8b333ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (318824 seconds ago): 31883, last successful... (3 Replies)
Discussion started by: Neo
3 Replies
o2image(8) OCFS2 Manual Pages o2image(8)
NAME
o2image - Copy or restore OCFS2 file system meta-data
SYNOPSIS
o2image [-r] [-I] device image-file
DESCRIPTION
o2image copies the OCFS2 file system meta-data from the device to the specified image-file. This image file contains the file system
skeleton that includes the inodes, directory names and file names. It does not include any file data.
This image file can be useful to debug certain problems that are not reproducible otherwise. Like on-disk corruptions. It could also be
used to analyse the file system layout in an aging file system with an eye towards improving performance.
As the image-file contains a copy of all the meta-data blocks, it can be a large file. By default, it is created in a packed format, in
which all meta-data blocks are written back-to-back. With the -r option, the user could choose to have the file in the raw (or sparse) for-
mat, in which the blocks are written to the same offset as they are on the device.
debugfs.ocfs2 understands both formats.
o2image also has the option, -I, to restore the meta-data from the image file onto the device. This option will rarely be useful to end-
users and has been written specifically for developers and testers.
OPTIONS
-r Copies the meta-data to the image-file in the raw format. Use this option only if the destination file system supports sparse files.
If unsure, do not use this option and let the tool create the image-file in the packed format.
-I Restores meta-data from the image-file onto the device. CAUTION: This option could corrupt the file system.
EXAMPLES
[root@node1 ~]# o2image /dev/sda1 sda1.out
Copies metadata blocks from /dev/sda1 device to sda1.out file
[root@node1 ~] o2image -I /dev/sda1 sda1.out
Use with CAUTION. Copies meta-data blocks from sda1.out onto the /dev/sda1 device.
SEE ALSO
debugfs.ocfs2(8) fsck.ocfs2(8)
AUTHORS
Oracle Corporation
COPYRIGHT
Copyright (C) 2007, 2010 Oracle. All rights reserved.
Version 1.4.3 February 2010 o2image(8)