Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
kernel-xen-2.6.18-92.1.10.el5
kmod-drbd82-xen-8.2.6-1.2.6.18_92.1.10.el5
drbd82-8.2.6-1.el5
thats the versions of the userland and kmods im using ... they look right to me?
unless you know of anything?
On Wed, Oct 22, 2008 at 7:46 PM, Ilo Lorusso <sneak147 at gmail.com> wrote:
> this should be it ...
>
> kernel: drbd1: Handshake successful: Agreed network protocol version 88
> kernel: drbd1: conn( WFConnection -> WFReportParams )
> kernel: drbd1: Starting asender thread (from drbd1_receiver [2771])
> kernel: drbd1: data-integrity-alg: <not-used>
> kernel: drbd1: State change failed: Device is held open by someone
> kernel: drbd1: state = { cs:WFReportParams st:Primary/Unknown
> ds:UpToDate/DUnknown r--- }
> kernel: drbd1: wanted = { cs:WFReportParams st:Secondary/Unknown
> ds:UpToDate/DUnknown r--- }
> kernel: drbd1: helper command: /sbin/drbdadm pri-lost-after-sb
> kernel: drbd1: Split-Brain detected, dropping connection!
> kernel: drbd1: self
> 4DD93271AEDF62DF:20C87600C399C2C1:C7388C506EB193E3:937AA12EA53A198F
> kernel: drbd1: peer
> EE338B6DC5660589:20C87600C399C2C1:C7388C506EB193E3:937AA12EA53A198F
> kernel: drbd1: helper command: /sbin/drbdadm split-brain
> kernel: drbd1: conn( WFReportParams -> Disconnecting )
> kernel: drbd1: error receiving ReportState, l: 4!
> kernel: drbd1: asender terminated
> kernel: drbd1: Terminating asender thread
> kernel: drbd1: tl_clear()
> kernel: drbd1: Connection closed
> kernel: drbd1: conn( Disconnecting -> StandAlone )
> kernel: drbd1: receiver terminated
> kernel: drbd1: Terminating receiver thread
>
> Ive attached my config aswell, just incase Ive got something wrong there..
>
> i'll double check my userspace utils and kmods versions so long ..
>
>
> global {
> usage-count no;
> }
> common {
> protocol C;
> }
> resource home {
> startup {
> become-primary-on both;
> wfc-timeout 120;
> }
>
> net {
> allow-two-primaries;
> after-sb-0pri discard-least-changes;
> after-sb-1pri call-pri-lost-after-sb;
> after-sb-2pri call-pri-lost-after-sb;
> }
> syncer {
> rate 44M;
> }
> disk {
> # on-io-error detach;
> }
>
> on hordepri.ipnetwork.co.za {
> device /dev/drbd1;
> disk /dev/sdb1;
> address 172.69.128.108:7789;
> meta-disk internal;
> }
> on hordesec.ipnetwork.co.za {
> device /dev/drbd1;
> disk /dev/sdb1;
> address 172.69.128.109:7789;
> meta-disk internal;
> }
> }
>
> On Wed, Oct 22, 2008 at 5:58 PM, David Coulson <david at davidcoulson.net> wrote:
>> What is the error from the other side? Only time I had this problem was when
>> user-space tools and kernel modules were a different version.
>>
>> Ilo Lorusso wrote:
>>>
>>> Hi
>>>
>>> How do I get my my data to sync automatically when im using drbd8.2
>>> with ocfs2 in a primary / primary mode
>>> after one of my nodes gets its network connectivity back .
>>>
>>> this is whats happening in the logs after the network connectivity returns
>>> ..
>>>
>>> and none of the nodes are in a primary / primary state anymore ..
>>>
>>> any help appreciated ..
>>>
>>> Thank You
>>> ...
>>>
>>> : drbd1: Split-Brain detected, 2 primaries, automatically solved. Sync
>>> from this node
>>> : drbd1: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapS
>>> ) pdsk( DUnknown -> UpToDate )
>>> : drbd1: Writing meta data super block now.
>>> : drbd1: meta connection shut down by peer.
>>> : drbd1: peer( Primary -> Unknown ) conn( WFBitMapS -> NetworkFailure
>>> ) pdsk( UpToDate -> DUnknown )
>>> : drbd1: asender terminated
>>> : drbd1: Terminating asender thread
>>> : drbd1: sock_sendmsg returned -104
>>> : drbd1: short sent ReportBitMap size=4096 sent=0
>>> : drbd1: Writing meta data super block now.
>>> : drbd1: sock was shut down by peer
>>> _______________________________________________
>>> drbd-user mailing list
>>> drbd-user at lists.linbit.com
>>> http://lists.linbit.com/mailman/listinfo/drbd-user
>>>
>>
>