search for: make_panic

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 will get hung. This issue also described in Novell bugzilla #492055 (https://bugzilla.novell.com/show_bug.cgi?id=492055). Now on upstream kernel, the dead-hang is not reproduced. But the accessing wil...

...worker_thread 3060 S< [dlm_send] worker_thread 3061 S< [dlm_recoverd] dlm_recoverd 3067 S< [kjournald2] kjournald2 3068 S< [ocfs2cmt] ocfs2_commit_thread 3082 D+ /usr/bin/perl /root/make_pa ocfs2_cluster_lock make_panic D 0000000000000002 0 3082 3021 ffff8801360f1a38 0000000000000046 ffffffffa0240b08 ffff88013703ea40 ffff88013eb877f8 0000000000004000 00000000001d0a80 000000000000cb10 0000000000000000 ffffffffa0240af0 ffff88013703ea40 ffff88007ffee340 Call Trace: [<ffffffffa022bdbf>] ? dlm_put_l...

This patch plugs a race between the downconvert thread and an unlock ast message. Specifically, after the downconvert worker has done its task, the dc thread needs to check whether an unlock ast made the downconvert moot. Reported-by: David Teigland <teigland at redhat.com> Signed-off-by: Sunil Mushran <sunil.mushran at oracle.com> Acked-by: Mark Fasheh <mfasheh at sus.com> ---

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 4 root root 4096 2009-05-08 15:29 .. -rw-r--r-- 1 root root 0 2009-05-08 15:33 file0000000001 -rw-r--r-- 1 root root 459611068 2009-05-08 15:33 file0000000003 then run this...

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