similar to: Quantifying OCFS2 network traffic...

Hi all, I'm trying to determine the performance implications of various configurations for ocfs2. (I'm new to ocfs2, but have read through all the docs for both 1.2 and 1.4, so please be gentle :) This would be a 1.4 installation. I searched through www.mail-archive.com and didn't see anything appropriate. If there are other links, please let me know. In my case, I want to

David, So here are the two patches. Remove all patches that you have and apply these. The first one is straight forward. The second one will hopefully fix the livelock issue you have been encountering. People reviewing the patches should note that the second one is slightly different than the one I posted earlier. It removes the BUG_ON in the if condition where we jump to update_holders. The

Please review the list of patches being applied to the ocfs2 1.4 tree. All patches list the mainline commit hash. Thanks Sunil

This email is also sent to cluster-devel at redhat.com. Since this issue is about both dlm and ocfs2, I send the email here to look for help from upstream. This is an already known issue. on ocfs2 with user space cluster stack, run the test script from http://people.redhat.com/~teigland/make_panic on the mounted ocfs2 volume from 2 nodes simultaneously, the access to ocfs2 volume on both nodes

These patches convert the mle list to a hash. The same patches apply on ocfs2 1.4 too. Currently, we use the same number of hash pages for mles and lockres'. This will be addressed in a future patch that will make both of them configurable. Sunil

Hi, we have recently started to use ocfs2 on some RHEL 5.5 servers (ocfs2-1.4.7) Some days ago, two servers sharing an ocfs2 filesystem, and with quite virtual services, stalled, in what it seems on ocfs2 issue. This are the lines in their messages files: =====node heraclito (0)======================================== /Dec 4 09:15:06 heraclito kernel: o2net: connection to node parmenides

The changes from the last drop are: 1. Patch 11 removes struct dlm_lock_name. 2. Patch 12 is an unrelated bugfix. Actually is related to a bugfix that we are retracting in mainline currently. The patch may need more testing. While I did hit the condition in my testing, Marcos hasn't. I am sending it because it can be queued for 2.6.30. Give us more time to test. 3. Patch 13 will be useful

Mainline commit d4f7e650e55af6b235871126f747da88600e8040 attempts to delay the dlm_thread from sending the drop ref message if the lockres is being migrated. The problem is that we make the dlm_thread wait for the migration to complete. This causes a deadlock as dlm_thread also participates in the lockres migration process. A better fix for the original oss bugzilla#1012 is in testing.

We have an application that has many processing threads writing more than a billion files ranging from 2KB ? 50KB, with 50% under 8KB (currently there are 700 million files). The files are never deleted or modified ? they are written once, and read infrequently. The files are hashed so that they are evenly distributed across ~1,000,000 subdirectories up to 3 levels deep, with up to 1000 files

hello, I'm running Ubuntu Breezy with the OCFS2 modules in the standard kernel. I installed ocfs2console and ocfs2-tools I've formatted a partition with ocfs2. But I can't add any node or mount the device(with the ocfs2console). because I get a "Unable to access cluster service" I can't find the cause nor the solution to this. root@lenaeja:~# /etc/init.d/o2cb status

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

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

The following series of patches comprises the bulk of our outstanding changes for Ocfs2. Aside from the usual set of cleanups and fixes that were inappropriate for 2.6.25, there are a few highlights: The '/sys/o2cb' directory has been moved to '/sys/fs/o2cb'. The new location meshes better with modern sysfs layout. A symbolic link has been placed in the old location so as to

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

Does anyone have any idea what to try next? Here are the steps I have taken and the problem: (I wanted to post my question on the first line before I explained the problem and what I have tried) ---------- Node 0 has the file system mounted just fine and works great. When trying to mount on Node 1: `mount.ocfs2 /dev/mapper/data /cluster/ data` I get this error after about 30 seconds:

All, This is hopefully the final drop of the patches for adding global heartbeat to the o2cb stack. The diff from the previous set is here: http://oss.oracle.com/~smushran/global-hb-diff-2010-10-07 Implemented most of the suggestions provided by Joel and Wengang. The most important one was to activate the feature only at the end, Also, got mostly a clean run with checkpatch.pl. Sunil

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