Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Which versions did you use? Today I updated the PPA and a few minutes ago I tried to reproduce your scenario. Works for me as expected (several rounds of "dd" on top of the ext4 fs). So please try to reproduce with the latest releases in the PPA (kernel module 9.0.3, utils 8.9.7, drbdmange 0.97) and report back if your problem still exists. Regards, rck (resending to trim contents into gists) I updated today after I saw the updated ppa bits on both nodes: <snip> drbd-dkms/xenial,now 9.0.3-1ppa1~xenial1 all [installed] drbd-utils/xenial,now 8.9.7-1ppa1~xenial1 amd64 [installed] python-drbdmanage/xenial,now 0.97-1ppa1~xenial1 all [installed] </snip> And both nodes to appear to be running the latest build: <snip> root at elysium-test01:~# drbdadm --version DRBDADM_BUILDTAG=GIT-hash:\ 7ea0389343845f8336793f9163f71e31133be6af\ build\ by\ buildd at lgw01-02\,\ 2016-07-15\ 09:15:48 DRBDADM_API_VERSION=2 DRBD_KERNEL_VERSION_CODE=0x090003 DRBDADM_VERSION_CODE=0x080907 DRBDADM_VERSION=8.9.7 root at elysium-test01:~# drbdmanage --version drbdmanage 0.97; GIT-hash: d0032c6a22c29812263ab34a6e856a5b36fd7da0 root at elysium-test01:~# cat /proc/drbd version: 9.0.3-1 (api:2/proto:86-111) GIT-hash: a14cb9c3818612dfb8c3288db28a591d5a0fc2a6 build by root at elysium-test01, 2016-07-15 17:48:17 Transports (api:14): tcp (1.0.0) </snip> <snip> root at elysium-test02:~# drbdadm --version DRBDADM_BUILDTAG=GIT-hash:\ 7ea0389343845f8336793f9163f71e31133be6af\ build\ by\ buildd at lgw01-02\,\ 2016-07-15\ 09:15:48 DRBDADM_API_VERSION=2 DRBD_KERNEL_VERSION_CODE=0x090003 DRBDADM_VERSION_CODE=0x080907 DRBDADM_VERSION=8.9.7 root at elysium-test02:~# drbdmanage --version drbdmanage 0.97; GIT-hash: d0032c6a22c29812263ab34a6e856a5b36fd7da0 root at elysium-test02:~# cat /proc/drbd version: 9.0.3-1 (api:2/proto:86-111) GIT-hash: a14cb9c3818612dfb8c3288db28a591d5a0fc2a6 build by root at elysium-test02, 2016-07-15 17:48:21 Transports (api:14): tcp (1.0.0) </snip> FTR I’m using just the standard gcloud ubuntu 16.04 image: <snip> ubuntu-1604-xenial-v20160627 Description Canonical, Ubuntu, 16.04 LTS, amd64 xenial image built on 2016-06-27 Creation time Jun 28, 2016, 2:54:42 AM </snip> And I did `apt upgrade` it before trying any of this. Linux elysium-test01 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Linux elysium-test02 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux * * * Problems still occur however. I ran into this just now when testing mounting/unmounting the volume on the 2 nodes. This happened when unmounting on elysium-test02, logs from elysium-test01: https://gist.github.com/jdillon/a823d7e4e9184c9ea6bb7df3e2fd9216 And the umount process on elysium-test02 is now wedged, with logs: https://gist.github.com/jdillon/6126028d7cb2210f35edc0393ae60dca FTR I tried this a bunch of times and it worked as expected once or twice, then freaked out. :-( —jason -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20160716/53100da9/attachment.htm>