Comment 10 for bug 1185756

Dear Stefan Bader (smb),
I installed the 64-bits package you posted on 1 node of each cluster and it worked mostly as expected indeed.

The first cluster has kernel 3.8.
It had tools 8.4.2 installed from the sources. I uninstalled them (make unsintall was a bit buggy in that version but no mater), and replaced with your package.
drbdadm --version now shows :
DRBDADM_BUILDTAG=GIT-hash:\ 89a294209144b68adb3ee85a73221f964d3ee515\ build\ by\ phil@fat-tyre\,\ 2013-02-05\ 15:35:49
DRBDADM_API_VERSION=1
DRBD_KERNEL_VERSION_CODE=0x080402
DRBDADM_VERSION_CODE=0x080403
DRBDADM_VERSION=8.4.3

The second cluster has kernel 3.2. (backported by your humble servant)
It had tools and module v8.3.13 installed from a custom package backported by you humble servant
I upgraded to you package and drbdadm now shows :
DRBDADM_BUILDTAG=GIT-hash:\ 89a294209144b68adb3ee85a73221f964d3ee515\ build\ by\ phil@fat-tyre\,\ 2013-02-05\ 15:35:49
DRBDADM_API_VERSION=88
DRBD_KERNEL_VERSION_CODE=0x08030d
DRBDADM_VERSION_CODE=0x08030a
DRBDADM_VERSION=8.3.10

On the second cluster, 2 out of 6 resources failed to reconnect gracefully, citing a mismatch in verify-alg. drbdadm --adjust all on the upgraded node brought it back in order.

In both clusters, the drbd config was left untouched (I refused the packaged version of the config file).
The module was not unloaded and primary resources remained in production.

Lionel Sausin.