Aimar Marco
2008-Mar-05 09:14 UTC
[Ocfs2-users] ocfs2 and another node is heartbeating in our slot
Hello, I have one cluster drbd8+ocfs2. If I mount ocfs2 partition on node1 it's work but when I mount partition on node 2 I receive in /var/log/messages this -Mar 5 18:10:04 suse4 kernel: (2857,0):o2hb_do_disk_heartbeat:665 ERROR: Device "drbd1": another node is heartbeating in our slot! -Mar 5 18:10:04 suse4 kernel: WARNING: at include/asm/dma-mapping.h:44 dma_map_sg() -Mar 5 18:10:04 suse4 kernel: [<e0e834a4>] ata_qc_issue+0x294/0x445 [libata] .... cluster.conf cluster: node_count = 2 name = susecluster node: ip_port = 7777 ip_address = 192.168.0.86 number = 0 name = suse3 cluster = susecluster node: ip_port = 7777 ip_address = 192.168.0.87 number = 1 name = suse4 cluster = susecluster drbd.conf global { usage-count yes; } common { syncer { rate 100M; } startup { #degr-wfc-timeout 0; #wfc-timeout 10; #become-primary-on both; } disk { on-io-error detach; } } resource drbd0 { protocol C; net { allow-two-primaries; after-sb-0pri disconnect; after-sb-1pri disconnect; after-sb-2pri disconnect; rr-conflict disconnect; } on suse3 { device /dev/drbd0; disk /dev/sda3; address 192.168.0.86:7789; meta-disk internal; } on suse4 { device /dev/drbd1; disk /dev/sda3; address 192.168.0.87:7789; meta-disk internal; } } on node1 /var/log/message Mar 5 18:19:05 suse3 kernel: o2net: accepted connection from node suse4 (num 1) at 192.168.0.87:7777 Mar 5 18:19:09 suse3 kernel: ocfs2_dlm: Node 1 joins domain 910AE33AD0A9410DB25AB317481A9B51 Mar 5 18:19:09 suse3 kernel: ocfs2_dlm: Nodes in domain ("910AE33AD0A9410DB25AB317481A9B51"): 0 1 thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20080305/aa5d7129/attachment.html
Apparently Analagous Threads
- Problem with mdadm + lvm + drbd + ocfs ( sounds obvious, eh ? :) )
- Recover botched drdb gfs2 setup .
- DRBD on a xen host: crash on high I/O
- Using XEN 4.1 to run Windows 7 DOMU on SERVER1, replicated the HVM to SERVER2 using DRBD. Win7 DOMU doesn't boot in SERVER2 after replication
- drbd