similar to: [Patch] ocfs2: remove the /sys/o2cb symlink

Hi Greg, The following two patches move /sys/o2cb into /sys/fs/o2cb as we previously discussed. A symlink is created to maintain compatibility with existing versions of ocfs2-tools. A patch to automatically search /sys/fs/o2cb has been committed to the ocfs2-tools repo and a release with that code shouldn't be too far out. Old versions of ocfs2-tools have been tested and work fine with the

Hi, I might be overlooking the obvious, but I have yet to find "/etc/init.d/o2cb" however, I read that configuration uses this init script. Where is it? From: ocfs2-tools-1.2.4/README.O2CB [Starting the OCFS2 Clustering Services] O2CB is comprised of a simple node manager, heartbeat, TCP protocol, and DLM. The basic steps in startup are as follows: 1) Load the nodemanager,

I was testing ocfs2 on a 2 node cluster set up. ocfs2-tools version is 1.6.3 ocfs2 kernel version is 2.6.36 Using cman on 2 nodes node02 dw # ping_pong -rwm /data/test.dat 3 data increment = 2 14 locks/sec node01 dw # ping_pong -rw /data/test.dat 3 data increment = 2 10 locks/sec node02 dw # ping_pong -r /data/test.dat 3 1980 locks/sec Using cman on 1 node node02 dw #

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, When I installed ocfs2 the first time and setup oracle to work with it, the clustername defaulted to "ocfs2". We are testing adding new nodes, but we would like to add new nodes to the o2cb cluster in a different clustername. Do I need to do anything to keep that separate on the filesystem. I just want to make sure that when

Hello, I have a DELL MD3000i, and a couple of servers that I want to connect to the array. I have setup the main server with CentOS 5. - 2.6.18-53.el5 x86_64 - ocfs2-tools-1.2.7-1.el5 - ocfs2console-1.2.7-1.el5 - ocfs2-2.6.18-53.el5-1.2.8-2.el5 # Kernel Module And two OpenSuSe 10.3 Servers - 2.6.22.5-31-default x86_64 - ocfs2-tools-1.2.6-18 - ocfs2console-1.2.6-18 The module has been already

V1 -> V2: Move kmalloc() before mutex_lock(), suggested by Arjan. file_remove_suid() should be called with i_mutex held, file_update_time() too. So move them after mutex_lock(). Plus, check the return value of kmalloc(). Signed-off-by: WANG Cong <amwang@redhat.com> Cc: Arjan <arjan@infradead.org> Cc: Chris Mason <chris.mason@oracle.com> Cc: Yan Zheng

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

file_remove_suid() should be called with i_mutex held, file_update_time() too. So move them after mutex_lock(). Plus, check the return value of kmalloc(). Signed-off-by: WANG Cong <amwang@redhat.com> --- diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c index 7c3cd24..cd36301 100644 --- a/fs/btrfs/file.c +++ b/fs/btrfs/file.c @@ -944,14 +944,17 @@ static ssize_t btrfs_file_write(struct file

Hi, as far as I understand the current situation with locking looks like this: - o2cb supports cluster-aware flock(2). fcntl(2) locks are only local. - Pacemaker and cman also support cluster-aware fcntl(2) - There is no way for a userspace program to check if fcntl(2) is cluster- aware or not Is this correct? We would like to stick with the o2cb cluster stack but there are applications like

Seems RPM compatibility issue with OS Kernel. Check OS Kernel and download RPM (4 Nos) for same kernel. Regards, Yuvrajsinh Chauhan || Sr. DBA || CRESTEL-PSG Elitecore Technologies Pvt. Ltd. 904, Silicon Tower || Off C.G.Road Behind Pariseema Building || Ahmedabad || INDIA [GSM]: +91 9727746022 -----Original Message----- From: ocfs2-users-bounces at oss.oracle.com [mailto:ocfs2-users-bounces

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:

Hi Yuvrajsinh, thank you for the reply, yes it was a kernel issue and we have done an upgrade to 2.6.18.308 and used the packges that match the version number, and I have done a update post this evening as below Hi All, since the post I have made some kind of a progress 1. I upgraded the kernel to 2.6.18-308.1.1.el5 same I was able to download the ocfs2 module is

Hello All, I have multiple OCFS2 clusters on SLES10 SP2 running Xen. We needed to increase the O2CB_HEARTBEAT_THRESHOLD from 31 up to 61 and did so successfully on 2 of our 3 clusters. However on one of the three clusters we are not able to change the value. The /etc/sysconfig/o2cb file contains 61 as the threshold after reconfiguring via /etc/init.d/o2cb configure, we reconfigure all 3 nodes at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, another problem I did not find a solution for... I ran "o2cb configure" and configured a cluster named "ocfs2". Lazy me, I did not invent a new name. Now this cluster must be renamed to avoid confusion, the name has to change to "sapcluster". I changed /etc/ocfs2/cluster.conf to the new name and ran

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, I am trying to configure a two node cluster on SLES10SP2 using user level heartbeat. Here is my configuration. ocfs2-tools-1.4.0-0.3 **user level heartbeat** -> lsmod | grep ocfs ocfs2_user_heartbeat 20992 1 ocfs2_dlmfs 37776 1 ocfs2_dlm 204456 1 ocfs2_dlmfs ocfs2_nodemanager 223384 6 ocfs2_user_heartbeat,ocfs2_dlmfs,ocfs2_dlm configfs 44700 3 ocfs2_user_heartbeat,ocfs2_nodemanager

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

Hello, this is my scenario: 1)I've created a Pacemaker cluster with the following ocfs package on opensuse 11.3 64bit ocfs2console-1.8.0-2.1.x86_64 ocfs2-tools-o2cb-1.8.0-2.1.x86_64 ocfs2-tools-1.8.0-2.1.x86_64 2)I've configured the cluster as usual : <resources> <clone id="dlm-clone"> <meta_attributes id="dlm-clone-meta_attributes">

Thanks for a great file system! I have a two-node cluster working as a HA NFS server. This system has worked fine for almost a year, but recently I found that an ocfs2 file system had been corrupted and needed to be repaired with fsck.ocfs2. Even though I don't think that any data was lost I found that 4 of my 14 ocfs2 partitions had some errors which were corrected by fsck.ocfs2. I then

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.