search for: fs_lock

Hello, We just experienced a hang that looks superficially very similar to http://www.mail-archive.com/ocfs2-users at oss.oracle.com/msg02359.html There are 3 nodes in the cluster ocfs2-1.4.1 rhel 5.2. Versions, uname's in the attached text file which also includes fs_locks dumps and various other diagnostics. The lock up happened when we were restarting a java application that was writing to the /journal directory, being read by another java app on a second node. Restarting the machine that the jvm was running on did not help - indicating a locking issue. ls...

...: As we test with two node in one OCFS2 cluster. The cluster is hang up may be for dead lock. We use the debugfs.ocfs tool founding that one resource is holding by one node who has it for long time and another node can still wait for the resource. So the cluster is hang up. debugfs.ocfs2 -R "fs_locks -B" /dev/dm-0 debugfs.ocfs2 -R "dlm_locks LOCKID_XXX" /dev/dm-0 How to unlock the lock held by the node? Is there some commands to unlock the resource? Thanks. -------------------------------------------------------------------------------------------------------------------------...

...: As we test with two node in one OCFS2 cluster. The cluster is hang up may be for dead lock. We use the debugfs.ocfs tool founding that one resource is holding by one node who has it for long time and another node can still wait for the resource. So the cluster is hang up. debugfs.ocfs2 -R "fs_locks -B" /dev/dm-0 debugfs.ocfs2 -R "dlm_locks LOCKID_XXX" /dev/dm-0 How to unlock the lock held by the node? Is there some commands to unlock the resource? Thanks. -------------------------------------------------------------------------------------------------------------------------...

...ine on the "active" server. The command on the other nodes will hang / wait. Ls of another file in another path will work somtimes... After some minutes (3 - 15) all nodes can access the file, load is getting back, IO is normal again. But this isn't reproducable. debugfs.ocfs2 with fs_lock won't work regarding an mismatch between kernel and ocft-tools (I think). debugfs.ocfs2 -R "fs_locks" /dev/mapper/myocfs --> Debug string proto 3 found, but 2 is the highest I understand. - Why does this problem occure only since ~1 week? Why run the ocfs fine weeks before? (I'...

Hi! Seems we're facing some memory leak here. This is vanilla 2.6.19-rc6 on a x86_64 box, 4GB RAM. A simple `ls -Rn' on a filesystem with lots of files makes the box leak so much RAM that the OOM killer starts to kick in. With slab alloc debugging turned on, we see this: # mount; ls -Rn; wait some seconds; Ctrl-C [root@lnxp-1038:/backend1]$ cat /proc/slab_allocators | egrep

...flush_asts:596 ERROR: status = -107 CAS2/logdir/var/log/syslog.1-6785-Sep 16 20:57:16 CAS2 kernel: [516366.623997] Connect node 1 OK, and set timeout 0 CAS2/logdir/var/log/syslog.1-6786-Sep 16 20:57:17 CAS2 kernel: [516367.623592] o2net: Connected to node CAS1 (num 1) at 10.172.254.1:7100 debugfs: fs_locks -B Lockres: M00000000000000046e011700000000 Mode: Protected Read Flags: Initialized Attached Busy RO Holders: 0 EX Holders: 0 Pending Action: Convert Pending Unlock Action: None Requested Mode: Exclusive Blocking Mode: No Lock PR > Gets: 318317 Fails: 0 Waits (usec) Total: 128622 Max:...

Hi, everyone And we have the blocked cluster several times, and the log is always, we have to reboot all the node of the cluster to avoid it. Is there any patch that had fix this bug? [<ffffffff817539a5>] schedule_timeout+0x1e5/0x250 [<ffffffff81755a77>] wait_for_completion+0xa7/0x160 [<ffffffff8109c9b0>] ? try_to_wake_up+0x2c0/0x2c0 [<ffffffffa0564063>]

Hi, everyone And we have the blocked cluster several times, and the log is always, we have to reboot all the node of the cluster to avoid it. Is there any patch that had fix this bug? [<ffffffff817539a5>] schedule_timeout+0x1e5/0x250 [<ffffffff81755a77>] wait_for_completion+0xa7/0x160 [<ffffffff8109c9b0>] ? try_to_wake_up+0x2c0/0x2c0 [<ffffffffa0564063>]