similar to: disabling self-fencing

Hello everyone. I am currently working on setting up new servers for my employer. Basically we want two servers, all of them running several VEs (virtual environments, OpenVZ) which can dynamically take over each others job if necessary. Some services will run concurrently on both servers like apache2 (load balancing), so those need concurrent access to specific data. We had a close look at

Hi, According to comments in file fs/ocfs2/cluster/quorum.c:70 about the self-fencing operations : /* It should instead flip the file ?* system RO and call some userspace script. */ So, I tried to add it (but i did'nt find a way to flip the fs in RO). Here is a proposal for this functionnality, based on ocfs2-1.4.7. This patch add an entry 'fence_cmd' in /sys to specify an

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 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

Hi. I'm running RHEL4 for my test system, Adaptec Firewire controllers, Maxtor One Touch III shared disk (see the details below), 100Mb/s dedicated interconnect. It panics with no load about each 20 minutes (error message from netconsole attached) Any clues? Yegor --- [root at rac1 ~]# cat /proc/fs/ocfs2/version OCFS2 1.2.0 Tue Mar 7 15:51:20 PST 2006 (build

We're trying to setup a dual-primary DRBD environment, with a shared disk with either OCFS2 or GFS. The environment is a Centos 5.3 with DRBD82 (but also tried with DRBD83 from testing) . Setting up a single primary disk and running bonnie++ on it works. Setting up a dual-primary disk, only mounting it on one node (ext3) and running bonnie++ works When setting up ocfs2 on the /dev/drbd0

We're trying to setup a dual-primary DRBD environment, with a shared disk with either OCFS2 or GFS. The environment is a Centos 5.3 with DRBD82 (but also tried with DRBD83 from testing) . Setting up a single primary disk and running bonnie++ on it works. Setting up a dual-primary disk, only mounting it on one node (ext3) and running bonnie++ works When setting up ocfs2 on the /dev/drbd0

I am running a two-node web cluster on OCFS2 via DRBD Primary/Primary (v8.3.8) and Pacemaker. Everything seems to be working great, except during testing of hard-boot scenarios. Whenever I hard-boot one of the nodes, the other node is successfully fenced and marked ?Outdated? * <resource minor="0" cs="WFConnection" ro1="Primary" ro2="Unknown"

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, periodically one of on my two nodes cluster is fenced here are the logs: Jan 14 07:01:44 nvr1-rc kernel: o2net: no longer connected to node nvr2- rc.minint.it (num 0) at 1.1.1.6:7777 Jan 14 07:01:44 nvr1-rc kernel: (21534,1):dlm_do_master_request:1334 ERROR: link to 0 went down! Jan 14 07:01:44 nvr1-rc kernel: (4007,4):dlm_send_proxy_ast_msg:458 ERROR: status = -112 Jan 14 07:01:44

Hi, Not totally new to Xen but still very green and meeting some problems. Feel free to kick me to the DRBD people if this is not relevent here. I''ll be providing more info upon request but for now I''ll be brief. Debian/Squeeze running 2.6.32-5-xen-amd64 (2.6.32-21) Xen hypervisor 4.0.1~rc6-1 and drbd-8.3.8. One domU configured, with disk and swap image: root =

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.

Dear Sirs and Madams, I run a small visual effects production company, Hammerhead Productions. We'd like to have an easily extensible inexpensive relatively high-performance storage network using open-source components. I was hoping that OCFS2 would be that system. I have a half-dozen 2 TB fileservers I'd like the rest of the network to see as a single 12 TB disk, with the aggregate

I people, i install the ocfs in my virtual machine, with centos 5.3 and xen. But when i turn off the machine1, the ocfs start the fencing off the machine2. I read the doc in oracle.com, but could not solve the problem. Someone help? My conf and my package version. cluster.conf node: ip_port = 7777 ip_address = 192.168.1.35 number = 0 name = x1 cluster

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:~ #

I have four database servers in a high-availability, load-balancing configuration. Each machine has a mount to a common data source which is an OCFS2 v1.4 file-system. While working on three of the servers, I restarted the IP network and found after-wards the fourth machine hung. I could not reboot and could not unmount the ocfs2 partitions. I am pretty sure this was all caused by my taking down

I have 10 servers in a cluster running Debian Etch with 2.6.26-bpo.2 with a backport of ocfs2-tools-1.4.1-1 I'm using AoE to export the drives from a Debian Lenny server in the cluster. My problem is if I mount the ocfs2 partition on the server that is exporting it via AoE it fences the entire cluster. Looking at the logs exporting the ocfs2 partition doesn't give much information...

Hi all, A recent update to CentOS 5.9 has broken my cluster's ability to fence nodes. I have two Dell's which are both fenced via their DRAC6 cards. The current configuration in cluster.conf for the fencing devices is: <fencedevice agent="fence_drac5" cmd_prompt="admin1-&gt;" ipaddr="192.168.251.11" login="fencer" name="ms1-drac"

By default, o2cb fences the box by calling emergency_restart(). While this scheme works well in production, it comes in the way during testing as it does not let the tester take stack/core dumps for analysis. This patch allows user to dynamically change the fence method to panic() by: # echo "panic" > /sys/kernel/config/cluster/<clustername>/fence_method Signed-off-by: Sunil

I'm interested in the idea of sharing a bunch of SAS JBOD devices between two CentOS servers in an active-standby HA cluster sort of arrangement, and found something about using scsi3 persistent reservations as a fencing method. I'm not finding a lot of specifics about how this works, or how you configure two initiator systems on a SAS chain. I don't have any suitable