similar to: Where can I find formal document for DLM ?

Now the discussion moves to kernel space, I move the email from ocfs2-tools-devel to ocfs2-devel. The original discussion can be found from http://oss.oracle.com/pipermail/ocfs2-tools-devel/2009-June/001891.html Joel Becker Wrote: > On Sat, Jun 27, 2009 at 03:46:04AM +0800, Coly Li wrote: >> Joel Becker Wrote: >>> On Sat, Jun 27, 2009 at 03:00:05AM +0800, Coly Li wrote: >>

I observer interesting dentry number during the dlm stress testing. The ocfs2 cluster stack is user space "pcmk". creating a empty directory, ls -al: total 8 drwxr-xr-x 2 root root 4096 2009-05-08 15:29 . drwxr-xr-x 4 root root 4096 2009-05-08 15:29 .. run script make_panic on single node, for 10 seconds, ls -al: total 12 drwxr-xr-x 2 root root 4096 2009-05-08 15:33 . drwxr-xr-x

o2dlm join and leave messages are more than informational as they are required is debugging locking issues. This patch changes them from KERN_INFO to KERN_NOTICE. Signed-off-by: Sunil Mushran <sunil.mushran at oracle.com> --- fs/ocfs2/dlm/dlmdomain.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/ocfs2/dlm/dlmdomain.c b/fs/ocfs2/dlm/dlmdomain.c index

This patch makes the following needlessly global functions static: - stringify_lockname() - dlm_debug_put() Signed-off-by: Adrian Bunk <bunk at kernel.org> --- fs/ocfs2/dlm/dlmdebug.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) fec83555cf8467e5c932fa52177b8f567eb84d94 diff --git a/fs/ocfs2/dlm/dlmdebug.c b/fs/ocfs2/dlm/dlmdebug.c index 5f6d858..1b81dcb 100644 ---

We should check dlm->dlm_state under dlm->spinlock though maybe in this case it doesn't hurt. Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> --- fs/ocfs2/dlm/dlmdomain.c | 13 ++++++------- 1 files changed, 6 insertions(+), 7 deletions(-) diff --git a/fs/ocfs2/dlm/dlmdomain.c b/fs/ocfs2/dlm/dlmdomain.c index 6b5a492..ab82add 100644 --- a/fs/ocfs2/dlm/dlmdomain.c +++

Wether the dlm_lock needs to access lvb or not depends on dlm_lock_resource it belongs to. So a new parameter "struct dlm_lock_resource *res" is added to dlm_new_lock() so that we can know if we need to allocate lvb for the dlm_lock. And we have to make the lockres availale for calling dlm_new_lock(). Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> ---

Currently f_fsid of struct kstatfs returned from ocfs2_statfs() is undefined (at least it should be filled with 0). Since in some conditions, f_fsid value might be used as (f_fsid, ino) pare to uniquely identify a file, ocfs2 should return a defined unique f_fsid value from ocfs2_statfs(). This patch uses uuid_hash as a unique ID to initiate f_fsid value, the 32bits width is enough for ocfs2

In fs/ocfs2/dlmglue.c:ocfs2_cluster_lock(), after label 'out:' the code is: 1373 if (wait && arg_flags & OCFS2_LOCK_NONBLOCK && 1374 mw.mw_mask & (OCFS2_LOCK_BUSY|OCFS2_LOCK_BLOCKED)) { 1375 wait = 0; 1376 if (lockres_remove_mask_waiter(lockres, &mw)) 1377 ret = -EAGAIN; 1378

On Mon, Nov 22, 2004 at 09:37:19PM -0600, svn-commits@oss.oracle.com wrote: > Author: mfasheh > Date: 2004-11-22 21:37:18 -0600 (Mon, 22 Nov 2004) > New Revision: 1663 > > Modified: > branches/dlm-glue/src/journal.c > branches/dlm-glue/src/namei.c > branches/dlm-glue/src/ocfs.h > branches/dlm-glue/src/super.c > Log: > * ocfs_malloc was hardly used so

There are two problems in dlm_run_purgelist 1. If a lockres is found to be in use, dlm_run_purgelist keeps trying to purge the same lockres instead of trying the next lockres. 2. When a lockres is found unused, dlm_run_purgelist releases lockres spinlock before setting DLM_LOCK_RES_DROPPING_REF and calls dlm_purge_lockres. spinlock is reacquired but in this window lockres can get reused. This

Hello, Our static analysis tool finds some possible data races in the OCFS2 file system in Linux 6.4.0-rc6. In most calling contexts, the variables? such as res->lockname.name and res->owner are accessed with holding the lock res->spinlock. Here is an example: ? lockres_seq_start() --> Line 539 in dlmdebug.c ??? spin_lock(&res->spinlock); --> Line 574 in dlmdebug.c (Lock

Hello, Our static analysis tool finds some possible data races in the OCFS2 file system in Linux 6.4.0-rc6. In most calling contexts, the variables such as res->lockname.name and res->owner are accessed with holding the lock res->spinlock. Here is an example: lockres_seq_start() --> Line 539 in dlmdebug.c spin_lock(&res->spinlock); --> Line 574 in dlmdebug.c (Lock

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.

Hi, On 6/13/23 4:23 PM, Tuo Li wrote: > Hello, > > Our static analysis tool finds some possible data races in the OCFS2 file > system in Linux 6.4.0-rc6. > > In most calling contexts, the variables such as res->lockname.name and > res->owner are accessed with holding the lock res->spinlock. Here is an > example: > > lockres_seq_start() --> Line 539

Hi All We are getting the following errors on our 2 node RAC cluster and the Nodes reboots during this time . Does anybody knows what is causing this issue? Do we need to upgrade our OCFS . We are running Oracle9i RAC on Linux (Redhat ) $ uname -r 2.6.9-55.ELsmp Mar 23 06:03:55 oradb02 kernel: kernel BUG at /rpmbuild/smushran/BUILD/ocfs2-1.2.9/fs/ocfs2/dlm/dlmmaster.c:2300! Mar 23 06:03:55

Hi, with lockdep enabled, I get the warning below. I've verified it and it seems to be really correct - we acquire dlm->ast_lock and lockres->spinlock in different orders in dlm_queue_bast() and dlm_lockres_release_asm(). I'm not sure whether this can really lead to a deadlock and / or how to fix this... Honza ======================================================= [

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

Hi list, I have some problems testing ocfs2. My test consist in: #server1: dd if=/dev/random of=/ocfs2_1/test & #server1: dd if=/dev/random of=/ocfs2_2/test & #server1: dd if=/dev/random of=/ocfs2_3/test & ... #server1: dd if=/dev/random of=/ocfs2_12/test & #server1:<Ctrl><Alt><SysRQ>B After that, another node begin recovery. After some time (+- 3min),

Signed-off-by: Goldwyn Rodrigues <rgoldwyn at suse.com> --- fs/ocfs2/stack_user.c | 30 ++++++++++++++++++++++++++++-- 1 file changed, 28 insertions(+), 2 deletions(-) diff --git a/fs/ocfs2/stack_user.c b/fs/ocfs2/stack_user.c index 286edf1..1b18193 100644 --- a/fs/ocfs2/stack_user.c +++ b/fs/ocfs2/stack_user.c @@ -799,11 +799,31 @@ static int fs_protocol_compare(struct

Hello, I have an active, balanced webcluster with 2 SLES10SP2 nodes, both running ocfs2 with an iscsi target. The ocfs2 volume is mounted on both nodes. Everything works fine, except sometime the load on both systems go as high as 200, then both systems freeze, only reboot helps to regain control. I noticed that this behaviour does not occur when the cluster is NOT balanced. When the load on both