It is a bit odd. Ok, some warnings seems to be coming from pacemaker commands. Like the WARN: decode_transition_key: Bad UUID (crm-resource-3048) in sscanf result (3) for 0:0:crm-resource-3048
I guess the problem is this: Apr 22 21:55:43 storage0 lrmd: [1242]: info: RA output: (p_drbd_bigpool:0:start:stderr) drbdadm: Unknown command 'syncer' Apr 22 21:55:43 storage0 drbd[3079]: ERROR: bigpool: Called drbdadm -c /etc/drbd.conf syncer bigpool This would mean that drbdadm did not pass control on drbdadm-83. And that would only happen if the current version did not seem to be 8.3. That version number looks to be read from /proc/drbd and would reflect the version of the kernel module. At least as long as reading from /proc/drbd is not failing. Then it would fall back to a version number defined in the command (which would be wrong). Would have been interesting to find out whether calling "drbdadm syncer bigpool" manually would fail the same way but that would need another maintenance window. Maybe try to see what /proc/drbd is showing. I probably would suggest that we open a new bug report for the cluster case, so this one can be closed with the fix to drbdsetup. Then at least the direct usage seems to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1185756 Title: drbd8-utils not compatible with linux-lts-raring kernel in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
