Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi to all
About of my problem of DRBD replication, please see this link:
http://drbd.10923.n7.nabble.com/Replication-problems-constants-with-DRBD-8-3-10-td17896.html
After, I made these changes:
1- Changed the drbd version to 8.4.2
2- Changed the realtek NICs for Intel PRO/1000 Pt Dual Port Server Adapter
Not Changed:
- Multiple Volumes on one resource DRBD. I dont know if because i have 2
resources on DRBD 8.4.2 can be a problem?
- The memory RAM is Kingston non-ECC. I don't know if this is a probllem?
- All the Hardware is new
- I use workstations Asus and not Servers
- I use net data-integrity-alg md5 (I would not want to have that remove it)
Always the communication of DRBD are:
1- NIC to NIC
2- Bond active-backup with two NICs
On a previous post Mr. Lars Ellenberg tell me basically two things about
loss connection of DRBD:
1- fix those "upper layers" to not do what they are doing,
But I do not know how to do
2- With special purpose built fencing handlers,
we may be able to fix your setup so it will freeze IO during the
disconnected period, reconnect, and replay pending buffers,
without any reset.
But unfortunately when I ask him how do it, he does not answer me
Now I need to know if anyone else can help me,
or if Mr. lars is reading this message, please i am waiting your answer
This is my current status:
version: 8.4.2 (api:1/proto:86-101)
GIT-hash: 7ad5f850d711223713d6dcadc3dd48860321070c build by root at kvm5,
2013-06-16 13:44:51
0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r-----
ns:1693953 nr:0 dw:612877 dr:1794100 al:909 bm:859 lo:0 pe:0 ua:0 ap:0
ep:1 wo:f oos:118784
1: cs:Connected ro:Primary/Primary ds:UpToDate/UpToDate C r-----
ns:345900 nr:0 dw:65472 dr:331343 al:160 bm:198 lo:0 pe:0 ua:0 ap:0 ep:1
wo:f oos:0
Jul 11 17:39:07 kvm5 kernel: block drbd0: Digest mismatch, buffer modified
by upper layers during write: 25724616s +4096
Jul 11 17:39:07 kvm5 kernel: d-con r0: meta connection shut down by peer.
Jul 11 17:39:07 kvm5 kernel: d-con r0: sock was shut down by peer
Jul 11 17:39:07 kvm5 kernel: d-con r0: peer( Primary -> Unknown ) conn(
Connected -> BrokenPipe ) pdsk( UpToDate -> DUnknown )
Jul 11 17:39:07 kvm5 kernel: d-con r0: short read (expected size 16)
Jul 11 17:39:07 kvm5 kernel: block drbd0: new current UUID
E88665E04325590F:8698D68A2619C82D:A11E02897DDD3EB1:A11D02897DDD3EB1
Jul 11 17:39:07 kvm5 kernel: d-con r0: asender terminated
Jul 11 17:39:07 kvm5 kernel: d-con r0: Terminating asender thread
Jul 11 17:39:07 kvm5 kernel: d-con r0: Connection closed
Jul 11 17:39:07 kvm5 kernel: d-con r0: conn( BrokenPipe -> Unconnected )
Jul 11 17:39:07 kvm5 kernel: d-con r0: receiver terminated
Jul 11 17:39:07 kvm5 kernel: d-con r0: Restarting receiver thread
Jul 11 17:39:07 kvm5 kernel: d-con r0: receiver (re)started
Jul 11 17:39:07 kvm5 kernel: d-con r0: conn( Unconnected -> WFConnection )
Jul 11 17:39:08 kvm5 kernel: d-con r0: Handshake successful: Agreed network
protocol version 101
Jul 11 17:39:08 kvm5 kernel: d-con r0: conn( WFConnection -> WFReportParams
)
Jul 11 17:39:08 kvm5 kernel: d-con r0: Starting asender thread (from
drbd_r_r0 [1892])
Jul 11 17:39:08 kvm5 kernel: block drbd0: drbd_sync_handshake:
Jul 11 17:39:08 kvm5 kernel: block drbd0: self
E88665E04325590F:8698D68A2619C82D:A11E02897DDD3EB1:A11D02897DDD3EB1 bits:203
flags:0
Jul 11 17:39:08 kvm5 kernel: block drbd0: peer
42F068778E1693E5:8698D68A2619C82D:A11E02897DDD3EB1:A11D02897DDD3EB1 bits:0
flags:0
Jul 11 17:39:08 kvm5 kernel: block drbd0: uuid_compare()=100 by rule 90
Jul 11 17:39:08 kvm5 kernel: block drbd0: helper command: /sbin/drbdadm
initial-split-brain minor-0
Jul 11 17:39:08 kvm5 kernel: block drbd0: helper command: /sbin/drbdadm
initial-split-brain minor-0 exit code 0 (0x0)
Jul 11 17:39:08 kvm5 kernel: block drbd0: Split-Brain detected but
unresolved, dropping connection!
Jul 11 17:39:08 kvm5 kernel: block drbd0: helper command: /sbin/drbdadm
split-brain minor-0
Jul 11 17:39:08 kvm5 kernel: d-con r0: meta connection shut down by peer.
Jul 11 17:39:08 kvm5 kernel: d-con r0: conn( WFReportParams ->
NetworkFailure )
Jul 11 17:39:08 kvm5 kernel: d-con r0: asender terminated
Jul 11 17:39:08 kvm5 kernel: d-con r0: Terminating asender thread
Jul 11 17:39:08 kvm5 kernel: block drbd0: helper command: /sbin/drbdadm
split-brain minor-0 exit code 0 (0x0)
Jul 11 17:39:08 kvm5 kernel: d-con r0: conn( NetworkFailure -> Disconnecting
)
Jul 11 17:39:08 kvm5 kernel: d-con r0: error receiving ReportState, e: -5 l:
0!
Jul 11 17:39:08 kvm5 kernel: d-con r0: Connection closed
Jul 11 17:39:08 kvm5 kernel: d-con r0: conn( Disconnecting -> StandAlone )
Jul 11 17:39:08 kvm5 kernel: d-con r0: receiver terminated
Jul 11 17:39:08 kvm5 kernel: d-con r0: Terminating receiver thread
--
View this message in context: http://drbd.10923.n7.nabble.com/Replication-problems-constants-with-DRBD-8-3-10-tp17896p18007.html
Sent from the DRBD - User mailing list archive at Nabble.com.