similar to: Heartbeat Timeout Threshold

Hi Guys i got two node RAC cluster Running on RHEL 5.0 .. i just want to what is oracle recomendid Defaults values for below mention parameters Thanks for your help Heartbeat dead threshold network idle timeout network keepalive delay in ms network reconnect delay in ms kernel.panic_on_oops kernel.panic Regards, Devender

We have a setup with 15 hosts fibre attached via a switch to a common SAN. Each host has a single fibre port, the SAN has two controllers each with two ports. The SAN is exposing four OCFS2 v1.4.2 volumes. While performing a failover test, we observed 8 hosts fence and 2 reboot _without_ fencing. The OCFS2 FAQ recommends a default disk heartbeat of 31 - 61 loops for multipath io users. Our initial

Hi I have: SLES 10 SP2 (2.6.16.60-0.21-smp) ocfs2-tools-1.4.0-0.3 ocfs2console-1.4.0-0.3 and I can't change "heartbeat dead threshold" value. Content of /etc/sysconfig/o2cb: # O2CB_ENABLED: 'true' means to load the driver on boot. O2CB_ENABLED=true # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=ocfs2 # O2CB_HEARTBEAT_THRESHOLD:

We just installed a new cluster with 6 HP DL380g5, dual single port Qlogic 24xx HBAs connected via two HP 4/16 Storageworks switches to a 3Par S400. We are using the 3Par recommended config for the Qlogic driver and device-mapper-multipath giving us 4 paths to the SAN. We do see some SCSI errors where DM-MP is failing a path after get a 0x2000 error from the SAN controller, but the path gets puts

Hi there I recently installed an OCFS2 filesystem on our FC-SAN. Everything seemed to work fine and I could read & write the filesystem from both servers that are mounting it. After a while though, writes coming from one node do not appear on the other node and vice versa. I am not sure what's causing this, and not very experienced at debugging filesystems. If anybody has any

One more follow on, The combination of kernel.panic=60 and kernel.printk=7 4 1 7 seems to have netted the culrptit: E01-netconsole.log:Jan 18 09:45:10 E01 (10,0):o2hb_write_timeout:137 ERROR: Heartbeat write timeout to device dm-12 after 60000 milliseconds E01-netconsole.log:Jan 18 09:45:10 E01 (10,0):o2hb_stop_all_regions:1517 ERROR: stopping heartbeat on all active regions.

Hi, Sunil or Tao, I have a 4 nodes OCFS2 cluster running OCFS2 1.2.8 on SuSE 9 SP4. When I tried to do failover testing (shutting down one node), the whole cluster hung (I can not even login to any server in the cluster). I have to bring all of them up and then be able to use the system. What kind of behavior is it? Is it the fence of OCFS2? Below is my configuration. aopcer13:~ #

Hello OCFS2 team, I'm currently looking at the OCFS2 code in linux-2.6.17.11, and i wander why OCFS2 performs its heartbeat on a disk region unlike on the network like many clustered services stack do. What is the requirement for a disk heartbeat ? Is there any way to tune this behaviour and change it into a network heartbeat ? -- Mathieu

Hi guys I installed ocfs2 on 4 node (redhat 4u3) on shared FC devices ( EMC storage ). So I've noticed several problems: 1. When I restart first node, it shutdown so slow and I have to power off machine. What is the problem, heartbeat timeout, dlm ? 2. What will happen when I plug off network cabel ( for interconnect ). What shoud I do, unmount ocfs2 volume on each node, stop ocfs2

Hello, How to mount a disk with ocfs2 FS in one node to another . Let ys say I have /dev/sda mounted on /u01 in node 1 . I need to access it from nod2 . Any solutions ? I am using ubuntu 8.10 Node 1 ====== root at 110:~# /etc/init.d/o2cb status Module "configfs": Loaded Filesystem "configfs": Mounted Module "ocfs2_nodemanager": Loaded Module

Greetings, Last night I manually unpresented and deleted a LUN (a SAN snapshot) that was presented to one node in a four node RAC environment running OCFS2 v1.4.1-1. The system then rebooted with the following error: Oct 21 16:45:34 ausracdb03 kernel: (27,1):o2hb_write_timeout:166 ERROR: Heartbeat write timeout to device dm-24 after 120000 milliseconds Oct 21 16:45:34 ausracdb03 kernel:

I have an OCFS2 filesystem on a coraid AOE device. It mounts fine, but with heavy I/O the server self fences claiming a write timeout: (16,2):o2hb_write_timeout:164 ERROR: Heartbeat write timeout to device etherd/e0.1p1 after 12000 milliseconds (16,2):o2hb_stop_all_regions:1789 ERROR: stopping heartbeat on all active regions. Kernel panic - not syncing: ocfs2 is very sorry to be fencing this

Hi, I want to share a partition of an external disk between 3 machines. It is located on a Sun StoreTek 3510 and bound (via multipathing) to all 3 machines. One machine (say mach1) is the node I used to create the filesystem and setup /etc/ocfs2/cluster.conf. I copied the file to the other 2 machines. All use the same /etc/multipath.conf[1], too. All start /etc/init.d/ocfs2 at boot, all are

Hi, I have installed and configured ocfs2 as per the given guidelines on two nodes. The output of the service status of o2cb and ocfs2 is as under: Node: rashida1 -------------------------------------------------- [root at rashida1 ~]# service o2cb status Driver for "configfs": Loaded Filesystem "configfs": Mounted Driver for "ocfs2_dlmfs": Loaded Filesystem

Hi, Does OCFS require NAS hardware to run or does normal PC hard disk work? Thanks, Pete -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20081219/1bc9110b/attachment.html

Hi, I have OCFS2 Cluster of 5 nodes running on RHEL 5.2 (kernel version 2.6.18-128.1.10.el5). I am getting error like Jun 24 09:26:54 alf2 kernel: (2095,0):o2net_connect_expired:1637 ERROR: no connection established with node 2 after 30.0 seco nds, giving up and returning errors. Jun 24 09:27:54 alf2 last message repeated 2 times Jun 24 09:29:24 alf2 last message repeated 3 times Jun

When I try and run the mkfs.ocfs2 command after I have updated all of the other nodes in the cluster with the new node information in cluster.conf I am getting the following error: mkfs.ocfs2 -b 4k -C 32K -L "ocfs2" -N 4 /dev/sdb1 mkfs.ocfs2 1.4.4 Cluster stack: classic o2cb Overwriting existing ocfs2 partition. mkfs.ocfs2: Could not create domain while initializing the dlm As this is

I just recently upgraded a box from i386 5.3 -> 5.4. The box has heartbeat packages installed from "extras:" heartbeat-pils-2.1.3-3.el5.centos heartbeat-stonith-2.1.3-3.el5.centos heartbeat-devel-2.1.3-3.el5.centos heartbeat-2.1.3-3.el5.centos The heartbeat daemon no longer starts.. the init script reports a success, as well as the logs: May 4 22:33:10 fc-fmcln02 heartbeat: [9344]:

Hi, I have added heartbeat mode as global, but when I do a mkfs and mount, and then check the mount, it says I am in local mode. Even /sys/kernel/config/cluster/ocfs2/heartbeat/mode says local. I am running CentOS with 3.x kernel, with ocfs2-tools-1.6.4-1118. mkfs -t ocfs2 -b 4K -C 1M -N 16 --cluster-stack=o2cb /dev/sdb mount -t ocfs2 /dev/sdb /mnt -o

Hi to all, this is My first time on this mailinglist. I have a problem with Ocfs2 on Debian etch 4.0 I'd like when a node go down or freeze without unmount the ocfs2 partition the heartbeat not fence the server that work well ( kernel panic ). I'd like disable or heartbeat or fencing. So we can work also with only 1 node. Thanks