similar to: fsck in startup scripts

Hello Everyone, I just ran fsck.ocfs2 on /dev/drbd0 which is a one gig partition on a vm with limited resource (100meg of ram). I am worried that the process crashed because it has not responded in the past hour or so? fsck.ocfs2 /dev/drbd0 fsck.ocfs2 1.6.4 [RECOVER_CLUSTER_INFO] The running cluster is using the cman stack with the cluster name ASTCluster, but the filesystem is configured for

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

We are setting up 2 new EL5 U4 machines to replace our current database servers running our demo environment. We use 3Par SANs and their snap clone options. The current production system we snap clone from is EL4 U5 with ocfs2 1.2.9, the new servers have ocfs2 1.4.3 installed. Part of the refresh process is to run fsck.ocfs2 on the volume to recover, but right now as I am trying to run it on our

I have a Fedora Core server running: Fedora Core release 4 (Stentz) kernel version: 2.6.15-1.1833_FC4smp ( I have also tried kernel version: 2.6.16-1.2108_FC4smp) I compiled the ocfs2 and ocfs2-tools using the following steps: # MODULES: tar zxvpf ocfs2-1.2.1.tar.gz cd ocfs2-1.2.1 ./configure make make install # TOOLS: tar zxf ocfs2-tools-1.2.1.tar.gz cd ocfs2-tools-1.2.1 ./configure

It is obsoleted since Dec 2005. Signed-off-by: WANG Cong <amwang at redhat.com> --- Documentation/ABI/obsolete/o2cb | 11 ----------- Documentation/ABI/removed/o2cb | 10 ++++++++++ Documentation/feature-removal-schedule.txt | 10 ---------- fs/ocfs2/cluster/sys.c | 9 --------- 4 files changed, 10 insertions(+), 30 deletions(-) --- diff

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

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,

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

Hello list, I have a ~10TB ocfs2 filesystem in a 8-node cluster. This sits on a logical volume (I know lv is not cluster aware, but I make sure no one touches the lv, while the cluster is running). The LV consists of 5x2TB multipath devices. I recently had errors like this on some nodes: OCFS2: ERROR (device dm-7): ocfs2_check_group_descriptor: Group Descriptor # 0 has bad signature File

-----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 am on SLES 10, SP1, x86_64, running the distribution rpm's of ocfs: ocfs2console-1.2.3-0.7 ocfs2-tools-1.2.3-0.7 I have a two node ocfs2 cluster configured. One node died (manual reset), and the second started immediately to have problems on accessing the file system for the following reason from the logs: Transport endpoint not connected. a mounted.ocfs2 on the still living

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

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

Hello all, I'm having trouble compiling ocfs2-tools-1.6.3 on slackware64-13.1 These are my configure flags (the last 2 I added after googling this problem, but didn't help): ./configure \ --sbindir=/sbin \ --bin=/bin \ --libdir=/usr/lib${LIBDIRSUFFIX} \ --sysconfdir=/etc \ --datadir=/etc/ocfs2 \ --sharedstatedir=/var/ocfs2 \ --libexecdir=/usr/libexec \

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

Ubuntu 14.04, drbd Hi On a drbd Primary node, when attempting to mount our cluster partition: sudo mount -t ocfs2 /dev/drbd1 /cluster we get: mount.ocfs2: Unable to access cluster service while trying to join the group We then call: sudo dpkg-reconfigure ocfs2-tools Setting cluster stack "o2cb": OK Starting O2CB cluster ocfs2: OK And all is well: Aug 22 13:48:23 uc1 kernel: [