Motivation
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
Aug 27 05:25:43 host9 kernel: [2547757.533648] RSP: 0018:ffff8801c93b3b40 EFLAGS: 00010292 Aug 27 05:25:43 host9 kernel: [2547757.579013] 00004000000005b4 00000000000005b4 00000000000008a0 0000000000000800 Aug 27 05:25:43 host9 kernel: [2547757.623329] [<ffffffffc060a2f0>] ? drbd_destroy_connection+0xf0/0xf0 [drbd] |
Case 4
| Code Block | ||||
|---|---|---|---|---|
| ||||
Aug 27 04:26:29 host4 kernel: [478357.442244] Modules linked in: pci_stub(E) vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nfsv3(E) rpcsec_gss_krb5(E) nfsv4(E) dns_resolver(E) tcp_diag(E) inet_diag(E) ipt_REJECT(E) nf_reject_ipv4(E) nf_log_ipv6(E) ip6t_rt(E) veth(E) drbd(E) ipmi_devintf(E) xt_multiport(E) nf_log_ipv4(E) nf_log_common(E) xt_LOG(E) xt_limit(E) xt_tcpudp(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) ip6table_filter(E) xt_conntrack(E) xt_state(E) iptable_filter(E) ip_tables(E) nf_conntrack_ipv6(E) nf_defrag_ipv6(E) nf_conntrack(E) ip6_tables(E) x_tables(E) nfsd(E) auth_rpcgss(E) nfs_acl(E) nfs(E) lockd(E) grace(E) fscache(E) sunrpc(E) 8021q(E) garp(E) mrp(E) bridge(E) stp(E) llc(E) lru_cache(E) libcrc32c(E) crc32c_generic(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) kvm_intel(E) kvm(E) irqbypass(E)<4>[478357.455870] Hardware name: Thomas-Krenn.AG X9DR3-F/X9DR3-F, BIOS 3.0a 07/31/2013 Aug 27 04:26:29 host4 kernel: [478357.460567] RSP: 0018:ffff8808534f7b40 EFLAGS: 00010292 Aug 27 04:26:29 host4 kernel: [478357.465530] RBP: ffff8808534f7c58 R08: ffff880858d28af0 R09: 0000000000000000 Aug 27 04:26:29 host4 kernel: [478357.470727] FS: 0000000000000000(0000) GS:ffff88085fa00000(0000) knlGS:0000000000000000 Aug 27 04:26:29 host4 kernel: [478357.476167] Stack: Aug 27 04:26:29 host4 kernel: [478357.483832] Call Trace: Aug 27 04:26:29 host4 kernel: [478357.489826] [<ffffffff814acf80>] ? sock_sendmsg+0x30/0x40 Aug 27 04:26:29 host4 kernel: [478357.498117] [<ffffffffc07b9efd>] ? w_send_dblock+0x9d/0x1c0 [drbd] Aug 27 04:26:29 host4 kernel: [478357.506710] [<ffffffffc07d02f0>] ? drbd_destroy_connection+0xf0/0xf0 [drbd] Aug 27 04:26:29 host4 kernel: [478357.515569] Code: 90 90 90 90 90 eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03 83 e2 07 f3 48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1 <f3> a4 c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 Aug 27 04:26:29 host4 kernel: [478357.538514] ---[ end trace 0d23089f3d6f0d23 ]--- |
...
We managed to do it, somehow. But I don't recommend it for production systems. There are too many hickups and not too much to gain unless you want to migrate to multi-node setups in which case I strongly recommend using new nodes anyway.
...
Former solution attempt: Packaging Upstream DRBD 8.x Kernel Module for Debian
Conclusion chain
Without checking mailing list archives it seems unlikely that an eventual severe problem with DRBD 8.4.6 (almost 16 months old now) still is not fixed in the current 8.x module eversion.
...
It might be a good idea to perform this every now and then:
| No Format |
|---|
dkms status |
...
Failure ;-(
Unfortunately the whole problem of an ever-rising load occured with DRBD module 4.8.4-1 too. Further research TBD.