Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I have just updated to drbd 9.0.9 - drbd-utils 9.1.0 from the proxmox4 repo. Context: # uname -r 4.10.17-2-pve # cat /proc/drbd version: 9.0.9-1 (api:2/proto:86-112) GIT-hash: f7b979e7af01813e031aac579140237640c94569 build by root at pve2, 2017-09-07 13:02:48 Transports (api:16): tcp (9.0.9-1) # drbdadm -V DRBDADM_BUILDTAG=GIT-hash:\ 3fc9d321f9f60e84d7dcdaac545fe8be4b280a63\ build\ by\ buildsystem at linbit\,\ 2017-09-05\ 12:10:39 DRBDADM_API_VERSION=2 DRBD_KERNEL_VERSION_CODE=0x090009 DRBD_KERNEL_VERSION=9.0.9 DRBDADM_VERSION_CODE=0x090100 DRBDADM_VERSION=9.1.0 Symptoms: Issuing a "drbdadm adjust" command results in a segfault: For instance: # drbdadm down vm-105-disk-1 # drbdadm adjust vm-105-disk-1 Segmentation fault And in syslog: Sep 7 20:53:00 pve2 kernel: [27499.269184] drbd vm-105-disk-1: Starting worker thread (from drbdsetup [21603]) Sep 7 20:53:00 pve2 kernel: [27499.273909] drbd vm-105-disk-1 pve1: Starting sender thread (from drbdsetup [21609]) Sep 7 20:53:00 pve2 kernel: [27499.276101] drbd vm-105-disk-1 pve3: Starting sender thread (from drbdsetup [21613]) Sep 7 20:53:00 pve2 kernel: [27499.315588] drbdadm[21601]: segfault at 78 ip 000000000040d954 sp 00007ffe2062f9b0 error 4 in drbdadm[400000+31000] The resource is left in a Diskless state. Happily, "drbdadm up" works, so one is able to get down and up the resource. The segfaults are breaking clean reboot of a node; all resources but control ones are left in Diskless state after node boot, and are to be adjusted manually (drbdadm down & up). bye, rob