Mailing List Archive

drbd-9.1.17 and drbd-9.2.6
Happy Halloween our spooky friends
Our latest release shows we've made some mends

To make sure your data processing has little delay
We have brought back our RDMA from decay

Our new DRBD encryption is meant to be scary
It will definitely make any unauthorized parties be wary

Our last update is meant to be seen
Our new TCP transport is so fast you'll scream

Hopefully, some of our enhancements save you from fright,
And please, have a great Halloween tonight!



In the second week in release-candidate status, we got minor fixes on
the 9.2 branch and nothing on the 9.1 branch. It feels ready now.

I just read over my announcements of rc.1 and rc.2 and wondered why I
described the news in such a confusing way. Trying it again:

TLS: If you want to enable TLS put this into your config

net {
tls yes;
}

More details, here:
https://linbit.com/drbd-user-guide/drbd-guide-9_0-en/#s-tcp_ip-tls


Load-balancing over multiple TCP connections:

net {
load-balance-paths yes;
}

For that to do something useful, you need to have multiple paths for a
connection in your config. See here for more:
https://linbit.com/drbd-user-guide/drbd-guide-9_0-en/#s-configuring-multiple-paths

As of this release, you can not use 'tls' and 'load-balance-paths' together.

The RDMA transport got several fixes and two new configuration options.


9.2.6 (api:genl2/proto:86-122/transport:19)
--------
* a series of fixes to the RDMA transport, making it compatible with
more recent Mellanox cards and fixes in general to the RDMA code
* Tuning parameter rdma-ctrl-(snd|rcv)buf-size for fine tuning
* Makefile updates for compiling with OFED
* optional TLS encryption for the TCP transport, based on kTLS with
TLS handshakes in userspace
* a new load-balancing TCP transport "lb-tcp" that establises all
configured paths in paralle and distributes the packet load
over them
* a new config net option 'load-balance-paths' that easens
the steps of renaming the transports tcp to tcp-legacy and
lb-tcp to tcp and the final removal of the older tcp
implementation
* changes merged from drbd-9.1.17
- fix a potential crash when configuring drbd to bind to a
non-existent local IP address (this is a regression of drbd-9.1.8)
- Cure a very seldom triggering race condition bug during
establishing connections; when you triggered it, you got an OOPS
hinting to list corruption
- fix a race condition regarding operations on the bitmap while
forgetting a bitmap slot and a pointless warning
- Fix handling of unexpected (on a resource in secondary role) write
requests
- Fix a corner case that can cause a process to hang when closing the
DRBD device, while a connection gets re-established
- Correctly block signal delivery during auto-demote
- Improve the reliability of establishing connections
- Do not clear the transport with `net-options --set-defaults`. This
fix avoids unexpected disconnect/connect cycles upon an `adjust`
when using the 'lb-tcp' or 'rdma' transports in drbd-9.2.
- New netlink packet to report path status to drbdsetup
- Improvements to the content and rate-limiting of many log messages
- Update compatibility code and follow Linux upstream development
until Linux 6.5

https://github.com/LINBIT/drbd/commit/36c922e6b26d558e256ed490a5e859afbbed08c3
https://pkg.linbit.com//downloads/drbd/9/drbd-9.1.17.tar.gz

https://github.com/LINBIT/drbd/commit/52144c0f90a0fb00df6a7d6714ec9034c7af7a28
https://pkg.linbit.com//downloads/drbd/9/drbd-9.2.6.tar.gz
_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user
Re: drbd-9.1.17 and drbd-9.2.6 [ In reply to ]
From: drbd-user-bounces@lists.linbit.com <drbd-user-bounces@lists.linbit.com> on behalf of Philipp Reisner <philipp.reisner@linbit.com>
Sent: 31 October 2023 16:07
To: drbd-announce@lists.linbit.com
Cc: drbd-user@lists.linbit.com
Subject: [DRBD-user] drbd-9.1.17 and drbd-9.2.6

Hi,

The tags for these releases don't seem to have made it it github yet. Is it possible to get them pushed? We'd like to see if the reported fixes address a crash/hang with drbd we've been seeing.

Thanks,
James



<6>[21236.721355] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg node004a-00-00: Preparing remote state change 2392587428
<6>[21236.723573] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg node004a-00-00: Committing remote state change 2392587428 (primary_nodes=0)
<6>[21236.726339] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg node004a-00-00: peer( Primary -> Secondary )
<6>[21236.730954] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg node004a-00-00: Preparing remote state change 1429741561
<6>[21236.733200] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg node004a-00-00: Committing remote state change 1429741561 (primary_nodes=0)
<6>[21236.733209] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg node004a-00-00: conn( Connected -> TearDown ) peer( Secondary -> Unknown )
<6>[21236.733211] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg/0 drbd1011 node004a-00-00: pdsk( UpToDate -> DUnknown ) repl( SyncTarget -> Off )
<6>[21236.733274] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg node004a-00-00: conn( TearDown -> Disconnecting )
<6>[21236.733509] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg node004a-00-00: Terminating sender thread
<6>[21236.733520] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg node004a-00-00: Starting sender thread (from drbd_r_d091f05c [1347328])
<3>[21236.765194] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg/0 drbd1011 node004a-00-00: ASSERTION __dec_rs_pending(peer_req->peer_device) >= 0 FAILED in free_waiting_resync_requests
<3>[21236.766022] drbd d091f05c-2423-4e61-a042-bff1d6065068-1-cfg/0 drbd1011: ASSERTION !drbd_interval_empty(i) FAILED in drbd_remove_peer_req_interval
<4>[21236.766904] ------------[ cut here ]------------
<2>[21236.766905] kernel BUG at mm/slub.c:384!
<4>[21236.767438] invalid opcode: 0000 [#1] SMP NOPTI
<4>[21236.767928] CPU: 5 PID: 1347328 Comm: drbd_r_d091f05c Tainted: P OE 5.15.0-85-generic #95~20.04.2
<4>[21236.768522] Hardware name: Supermicro SYS-5019D-FN8TP-5-NC041/X11SDV-4C-TP8F, BIOS 1.2 11/14/2019
<4>[21236.769341] RIP: e030:kfree+0x21f/0x250
<4>[21236.770436] Code: ff ff 49 89 da e9 d2 fe ff ff 48 8b 55 d0 4d 89 e9 41 b8 01 00 00 00 4c 89 d1 4c 89 e6 4c 89 f7 e8 76 fa ff ff e9 0b ff ff ff <0f> 0b 41 bd 00 f0 ff ff 45 31 f6 eb 84 e8 df 20 cd ff 66 90 eb a1
<4>[21236.772713] RSP: e02b:ffffc900491abc78 EFLAGS: 00010246
<4>[21236.773659] RAX: ffff888f24c9f000 RBX: ffff888f24c9f000 RCX: ffff888f24c9f010
<4>[21236.774353] RDX: 0000000001aef99a RSI: ffffc900491abc88 RDI: ffff888100040400
<4>[21236.775065] RBP: ffffc900491abcb8 R08: 0000000000000003 R09: 0000000000000001
<4>[21236.775746] R10: ffff888f24c9f000 R11: 00000000ffffffff R12: ffffea003c9327c0
<4>[21236.776456] R13: ffffffffc0ce188e R14: ffff888100040400 R15: ffffc900491abd68
<4>[21236.777231] FS: 0000000000000000(0000) GS:ffff889046d40000(0000) knlGS:0000000000000000
<4>[21236.777956] CS: e030 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[21236.778701] CR2: 00007f4adb7f0ff0 CR3: 000000010d9be000 CR4: 0000000000050660
<4>[21236.778708] Call Trace:
<4>[21236.781965] <TASK>
<4>[21236.782769] ? show_trace_log_lvl+0x1d6/0x2ea
<4>[21236.783574] ? show_trace_log_lvl+0x1d6/0x2ea
<4>[21236.784423] ? drbd_free_peer_req+0x10e/0x220 [drbd]
<4>[21236.785235] ? show_regs.part.0+0x23/0x29
<4>[21236.786076] ? __die_body.cold+0x8/0xd
<4>[21236.786931] ? __die+0x2b/0x37
<4>[21236.787734] ? die+0x30/0x60
<4>[21236.788575] ? do_trap+0xbe/0x100
<4>[21236.789451] ? do_error_trap+0x70/0xb0
<4>[21236.790299] ? kfree+0x21f/0x250
<4>[21236.791247] ? exc_invalid_op+0x53/0x70
<4>[21236.792091] ? kfree+0x21f/0x250
<4>[21236.792992] ? asm_exc_invalid_op+0x1b/0x20
<4>[21236.793899] ? drbd_free_peer_req+0x10e/0x220 [drbd]
<4>[21236.794826] ? kfree+0x21f/0x250
<4>[21236.795747] ? kfree+0x1f7/0x250
<4>[21236.796689] drbd_free_peer_req+0x10e/0x220 [drbd]
<4>[21236.797585] drain_resync_activity+0x6dc/0xc10 [drbd]
<4>[21236.798502] ? wake_up_q+0x50/0x90
<4>[21236.799421] ? mutex_unlock+0x25/0x30
<4>[21236.800318] conn_disconnect+0x199/0xa10 [drbd]
<4>[21236.801263] ? receive_twopc+0xa6/0x120 [drbd]
<4>[21236.802199] ? process_twopc+0x17e0/0x17e0 [drbd]
<4>[21236.803108] drbd_receiver+0x373/0x880 [drbd]
<4>[21236.804009] drbd_thread_setup+0x84/0x1e0 [drbd]
<4>[21236.804984] ? __drbd_next_peer_device_ref+0x1a0/0x1a0 [drbd]
<4>[21236.809238] kthread+0x127/0x150
<4>[21236.809246] ? set_kthread_struct+0x50/0x50
<4>[21236.809250] ret_from_fork+0x1f/0x30
<4>[21236.809258] </TASK>
<4>[21236.813193] Modules linked in: nls_iso8859_1 tcp_diag udp_diag inet_diag cls_cgroup sch_htb drbd_transport_tcp(OE) drbd(OE) lru_cache bridge stp llc xt_owner xt_multiport xt_hl xt_tcpudp xt_state xt_conntrack xt_NFLOG ip6table_raw iptable_raw ip6table_mangle iptable_mangle ip6table_nat iptable_nat nf_nat ip6table_filter ip6_tables iptable_filter bpfilter dell_rbu nfnetlink_log nfnetlink dcdbas i40e igb joydev input_leds ipmi_ssif mei_me mei intel_pch_thermal ioatdma dca acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel xen_pciback xen_netback xen_blkback pstore_blk xen_gntalloc xen_gntdev xen_evtchn ramoops reed_solomon pstore_zone xenfs ip_tables x_tables autofs4 raid10 raid0 multipath linear xen_privcmd zstd zstd_compress zram zfs(POE) zunicode(POE) zzstd(O) zlua(OE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) nf_conntrack
<4>[21236.814967] nf_defrag_ipv6 nf_defrag_ipv4 aufs raid1 dm_raid raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core i2c_i801 ahci xhci_pci efi_pstore xhci_pci_renesas drm i2c_smbus libahci wmi
<4>[21236.831354] ---[ end trace 419a98e99f44cc14 ]---
<4>[21236.957553] RIP: e030:kfree+0x21f/0x250
<4>[21236.959131] Code: ff ff 49 89 da e9 d2 fe ff ff 48 8b 55 d0 4d 89 e9 41 b8 01 00 00 00 4c 89 d1 4c 89 e6 4c 89 f7 e8 76 fa ff ff e9 0b ff ff ff <0f> 0b 41 bd 00 f0 ff ff 45 31 f6 eb 84 e8 df 20 cd ff 66 90 eb a1
<4>[21236.962061] RSP: e02b:ffffc900491abc78 EFLAGS: 00010246
<4>[21236.963466] RAX: ffff888f24c9f000 RBX: ffff888f24c9f000 RCX: ffff888f24c9f010
<4>[21236.964826] RDX: 0000000001aef99a RSI: ffffc900491abc88 RDI: ffff888100040400
<4>[21236.966144] RBP: ffffc900491abcb8 R08: 0000000000000003 R09: 0000000000000001
<4>[21236.967452] R10: ffff888f24c9f000 R11: 00000000ffffffff R12: ffffea003c9327c0
<4>[21236.968708] R13: ffffffffc0ce188e R14: ffff888100040400 R15: ffffc900491abd68
<4>[21236.970019] FS: 0000000000000000(0000) GS:ffff889046d40000(0000) knlGS:0000000000000000
<4>[21236.971371] CS: e030 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[21236.972680] CR2: 00007f4adb7f0ff0 CR3: 000000010d9be000 CR4: 0000000000050660
<0>[21236.974227] Kernel panic - not syncing: Fatal exception
<0>[21236.975569] Kernel Offset: disabled
_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user