search for: dlm_get_lock_resourc

...func (95bc84eb:504) 1196260129.36329:1196260129.36337) Nov 28 15:28:59 web-ha2 kernel: o2net: no longer connected to node web-ha1 (num 0) at 192.168.255.1:7777 Nov 28 15:28:59 web-ha2 kernel: (23315,0):dlm_do_master_request:1331 ERROR: link to 0 went down! Nov 28 15:28:59 web-ha2 kernel: (23315,0):dlm_get_lock_resource:915 ERROR: status = -112 Nov 28 15:29:18 web-ha2 sshd[23503]: pam_unix2(sshd:auth): conversation failed Nov 28 15:29:18 web-ha2 sshd[23503]: error: ssh_msg_send: write Nov 28 15:29:22 web-ha2 kernel: (23396,0):dlm_do_master_request:1331 ERROR: link to 0 went down! Nov 28 15:29:22 web-ha2 kernel: (...

...182.367221:1173341182.367224) Mar 8 03:06:32 groupwise-1-mht kernel: o2net: no longer connected to node groupwise-2-mht (num 2) at 192.168.1.3:7777 Mar 8 03:06:32 groupwise-1-mht kernel: (499,0):dlm_do_master_request:1330 ERROR: link to 2 went down! Mar 8 03:06:32 groupwise-1-mht kernel: (499,0):dlm_get_lock_resource:914 ERROR: status = -112 Mar 8 03:13:02 groupwise-1-mht kernel: (8476,0):dlm_send_proxy_ast_msg:458 ERROR: status = -107 Mar 8 03:13:02 groupwise-1-mht kernel: (8476,0):dlm_flush_asts:607 ERROR: status = -107 Mar 8 03:19:54 groupwise-1-mht kernel: (147,1):dlm_send_remote_unlock_request:356 ERRO...

...:44 nvr1-rc kernel: (21534,1):dlm_do_master_request:1334 ERROR: link to 0 went down! Jan 14 07:01:44 nvr1-rc kernel: (4007,4):dlm_send_proxy_ast_msg:458 ERROR: status = -112 Jan 14 07:01:44 nvr1-rc kernel: (4007,4):dlm_flush_asts:600 ERROR: status = -112 Jan 14 07:01:44 nvr1-rc kernel: (21534,1):dlm_get_lock_resource:917 ERROR: status = -112 Jan 14 07:02:19 nvr1-rc kernel: (3950,5):o2net_connect_expired:1664 ERROR: no connection established with node 0 after 35.0 seconds, giving up and returning errors. Jan 14 07:02:54 nvr1-rc kernel: (3950,5):o2net_connect_expired:1664 ERROR: no connection established wit...

...(Access res->owner) However, in the following calling contexts: dlm_deref_lockres_worker() --> Line 2439 in dlmmaster.c dlm_drop_lockres_ref_done() --> Line 2459 in dlmmaster.c lockname = res->lockname.name; --> Line 2416 in dlmmaster.c (Access res->lockname.name) dlm_get_lock_resource() --> Line 701 in dlmmaster.c if (res->owner != dlm->node_num) --> Line 1023 in dlmmaster.c (Access res->owner) The variables res->lockname.name and res->owner are accessed respectively without holding the lock res->spinlock, and thus data races can occur. I am not qu...

...ss res->owner) However, in the following calling contexts: ? dlm_deref_lockres_worker() --> Line 2439 in dlmmaster.c ??? dlm_drop_lockres_ref_done() --> Line 2459 in dlmmaster.c ????? lockname = res->lockname.name; --> Line 2416 in dlmmaster.c (Access res->lockname.name) ? dlm_get_lock_resource() --> Line 701 in dlmmaster.c ??? if (res->owner != dlm->node_num) --> Line 1023 in dlmmaster.c (Access res->owner) The variables res->lockname.name and res->owner are accessed respectively without holding the lock res->spinlock, and thus data races can occur. I am not...

...ef_done() --> Line 2459 in dlmmaster.c > lockname = res->lockname.name; --> Line 2416 in dlmmaster.c (Access > res->lockname.name) lockname won't changed during the lockres lifecycle. So this won't cause any real problem since now it holds a reference. > > dlm_get_lock_resource() --> Line 701 in dlmmaster.c > if (res->owner != dlm->node_num) --> Line 1023 in dlmmaster.c (Access > res->owner) Do you mean in dlm_wait_for_lock_mastery()? Even if owner changes suddenly, it will recheck, so I think it is also fine. Thanks, Joseph > > The var...

...4589 func (be795f6d:507) 1237124191.594238:1237124191.594242) Mar 15 14:39:47 ugc-1 kernel: o2net: no longer connected to node cod-2 (num 3) at 10.0.0.42:7777 Mar 15 14:39:47 ugc-1 kernel: (24452,0):dlm_do_master_request:1335 ERROR: link to 3 went down! Mar 15 14:39:47 ugc-1 kernel: (24452,0):dlm_get_lock_resource:912 ERROR: status = -112 Mar 15 14:40:17 ugc-1 kernel: (1743,0):o2net_connect_expired:1637 ERROR: no connection established with node 3 after 30.0 seconds, giving up and returning errors. Mar 15 14:44:29 ugc-1 kernel: (16225,0):dlm_do_master_request:1335 ERROR: link to 3 went down! Mar 15...

...522 now 1233748227.272666 dr 1233748167.271516 adv 1233748167.271532:1233748167.271533 func (300d6acb:500) 1233748167.271522:1233748167.271526) o2net: no longer connected to node soap02 (num 0) at 192.168.0.10:7777 (5244,2):ocfs2_dlm_eviction_cb:108 device (8,33): dlm has evicted node 0 (12281,1):dlm_get_lock_resource:913 F59B45831EEA41F384BADE6C4B7A932B:M000000000000000000001aa9d5b7e0: at least one node (0) to recover before lock mastery can begin (12281,1):dlm_get_lock_resource:967 F59B45831EEA41F384BADE6C4B7A932B:M000000000000000000001aa9d5b7e0: at least one node (0) to recover before lock mastery can be...

After upgrading from 2.6.28.10 to 2.6.29.3 I've saw following new errors in kernel log: May 12 14:46:41 falcon-cl5 May 12 14:46:41 falcon-cl5 (6757,7):ocfs2_read_locked_inode:466 ERROR: status = -22 Only one node is mounted volumes in cluster: /dev/sde on /home/apache/users/D1 type ocfs2 (rw,_netdev,noatime,heartbeat=local) /dev/sdd on /home/apache/users/D2 type ocfs2

Sorry i don`t copy everything: TEST-MAIL1# echo "ls //orphan_dir:0000"|debugfs.ocfs2 /dev/dm-0|wc debugfs.ocfs2 1.6.4 5239722 26198604 246266859 TEST-MAIL1# echo "ls //orphan_dir:0001"|debugfs.ocfs2 /dev/dm-0|wc debugfs.ocfs2 1.6.4 6074335 30371669 285493670 TEST-MAIL2 ~ # echo "ls //orphan_dir:0000"|debugfs.ocfs2 /dev/dm-0|wc debugfs.ocfs2 1.6.4 5239722 26198604

...o kernel: (snmpd,16452,10):dlm_wait_for_node_death:370 0D3E49EB1F614A3EAEC0E2A74A34AFFF: waiting 5000ms for notification of de ath of node 1 Dec 4 09:15:06 heraclito kernel: (httpd,4615,10):dlm_do_master_request:1334 ERROR: link to 1 went down! Dec 4 09:15:06 heraclito kernel: (httpd,4615,10):dlm_get_lock_resource:917 ERROR: status = -112 Dec 4 09:15:06 heraclito kernel: (python,20750,10):dlm_do_master_request:1334 ERROR: link to 1 went down! Dec 4 09:15:06 heraclito kernel: (python,20750,10):dlm_get_lock_resource:917 ERROR: status = -112 Dec 4 09:15:06 heraclito kernel: (vzlist,22622,7):dlm_wait_for_...

...ode1 Index 0: took 119968 ms to do msleep Jul 14 05:55:59 node1 *** ocfs2 is very sorry to be fencing this system by restarting *** The 'dlm_send_remote_convert_request' and 'dlm_wait_for_node_death' on nodes 2 and 3 (and 4) then continued until: Jul 14 05:58:02 node3 (3542,2):dlm_get_lock_resource:921 98F84EF9EC254C499F79F8C13C57CF2E:$RECOVERY: at least one node (0) torecover before lock mastery can begin Jul 14 05:58:02 node3 (3542,2):dlm_get_lock_resource:955 98F84EF9EC254C499F79F8C13C57CF2E: recovery map is not empty, but must master $RECOVERY lock now Jul 14 05:58:02 node2 (3479,2):oc...

...ed:1667 ERROR: no connection established with node 3 after 30.0 seco nds, giving up and returning errors. Jul 29 10:17:27 alf1 last message repeated 2 times Jul 29 10:17:30 alf1 kernel: (2618,0):ocfs2_dlm_eviction_cb:98 device (8,33): dlm has evicted node 3 Jul 29 10:17:32 alf1 kernel: (2629,2):dlm_get_lock_resource:844 7BE7E9E2026A40F8801B56257D805C88:$RECOVERY: at least one node (3) to recover before lock mastery can begin Jul 29 10:17:32 alf1 kernel: (2629,2):dlm_get_lock_resource:878 7BE7E9E2026A40F8801B56257D805C88: recovery map is not empty, but must master $RECOVERY lock now Jul 29 10:17:32 alf1...

...main 129859624F7042EAB9829B18CA65FC88 Mar 2 10:20:57 xirisoas3 kernel: ocfs2_dlm: Nodes in domain ("129859624F7042EAB9829B18CA65FC88"): 1 2 3 4 Mar 3 16:18:02 xirisoas3 kernel: o2net: no longer connected to node XIRISOAS2 (num 2) at 10.0.0.5:9999 Mar 3 16:18:04 xirisoas3 kernel: (23344,2):dlm_get_lock_resource:921 129859624F7042EAB9829B18CA65FC88:$RECOVERY: at least one node (2) torecover before lock mastery can begin Mar 3 16:18:04 xirisoas3 kernel: (23344,2):dlm_get_lock_resource:955 129859624F7042EAB9829B18CA65FC88: recovery map is not empty, but must master $RECOVERY lock now Mar 3 16:18:04 xirisoas...

...rate_dir 16533 D mkdir dlm_wait_for_lock_mastery 31195 D+ ls iterate_dir So the code reviewed, and I found the order of the lock may wrong. In the function dlm_master_request_handler, the resource lock is held and so after the lock of &dlm->master_lock is locked. But in the function dlm_get_lock_resource, the &dlm->master_lock is locked first and so resource lock. They are different order in different function. If there are two task, one holds the res->lock waiting for the dlm->master_lock, with the function dlm_master_request_handler. Another task holds the &dlm->master_lock w...

...rate_dir 16533 D mkdir dlm_wait_for_lock_mastery 31195 D+ ls iterate_dir So the code reviewed, and I found the order of the lock may wrong. In the function dlm_master_request_handler, the resource lock is held and so after the lock of &dlm->master_lock is locked. But in the function dlm_get_lock_resource, the &dlm->master_lock is locked first and so resource lock. They are different order in different function. If there are two task, one holds the res->lock waiting for the dlm->master_lock, with the function dlm_master_request_handler. Another task holds the &dlm->master_lock w...

Does anybody knows if is there a certified procedure in to backup a RAC DB 10.2.0.3 based on OCFS2 , via split mirror or snaphots technology ? Using Linux LVM and OCFS2, does anybody knows if is possible to dinamically extend an OCFS filesystem, once the underlying LVM Volume has been extended ? Thanks in advance Riccardo Paganini

Hello! Hey didnt a setting for the 10 second network timeout get into the 2.6.20 kernel? if so how do we set this? I am getting OCFS2 1.3.3 (2201,0):o2net_connect_expired:1547 ERROR: no connection established with node 1 after 10.0 seconds, giving up and returning errors. (2458,0):dlm_request_join:802 ERROR: status = -107 (2458,0):dlm_try_to_join_domain:950 ERROR: status = -107

...0):ocfs2_write_begin_nolock:1722 ERROR: status = -5 (2872,0):ocfs2_write_begin:1860 ERROR: status = -5 (2872,0):ocfs2_file_buffered_write:2039 ERROR: status = -5 (2872,0):__ocfs2_file_aio_write:2194 ERROR: status = -5 (2065,0):ocfs2_dlm_eviction_cb:98 device (8,33): dlm has evicted node 2 (12701,1):dlm_get_lock_resource:844 6A03E81A818641A68FD8DC23854E12D3:M00000000000000000000243568d3c5: at least one node (2) to recover before lock mastery can begin (2045,0):ocfs2_dlm_eviction_cb:98 device (8,33): dlm has evicted node 2 (12701,1):dlm_get_lock_resource:898 6A03E81A818641A68FD8DC23854E12D3:M00000000000000000000243...

...80 dr 1158758358.807964adv 1158758358.808000:1158758358.808001 func (23633ca3:504) 1158757938.878265: 1158757938.878271) Sep 20 15:20:02 src-rac-duplicati1 kernel: (10047,0):ocfs2_replay_journal:1174 Recovering node 1 from slot 0 on device (104,1) Sep 20 15:20:05 src-rac-duplicati1 kernel: (2062,1):dlm_get_lock_resource:847 6AEF3479C4784E9895BDE697EFCAC035:$RECOVERY: at least one node (1) torecover before lock mastery can begin Sep 20 15:20:05 src-rac-duplicati1 kernel: (2062,1):dlm_get_lock_resource:874 6AEF3479C4784E9895BDE697EFCAC035: recovery map is not empty, but must master $RECOVERY lock now Can you help...