Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Thu, Apr 24, 2014 at 04:10:56PM +0100, Brian Candler wrote: > drbd 8.4.x contains compatibility executables drbdsetup-83 and > drbdadm-83, which are exec()'d if the userland detects that the > kernel is running drbd 8.3. > > However there is a case where this doesn't seem to be compatible. > > "ganeti" issues the following drbdsetup command: drbdadm is (at least *supposed* to be) able to deal with backwards compatibility. drbdsetup is only compatible where it happens to be so. Anything using drbdsetup directly should know what it is doing, and call the correct binary. In general we recommend to use the userland matching the module. > drbdsetup /dev/drbd2 disk > /dev/xenvg/a614fd3b-d016-44a1-a6d6-c51334190757.disk0_data > /dev/xenvg/a614fd3b-d016-44a1-a6d6-c51334190757.disk0_meta 0 -e > detach --create-device -d 1024m > > This is accepted (silently, exitcode 0) by drbdsetup from 8.3.10. > It's also accepted if you pass it explicitly to > /lib/drbd/drbdsetup-83. > > However if you pass this to drbdsetup in 8.4 it is rejected with a > "USAGE: drbdsetup command device arguments options" error. So the > frontend drbdsetup is rejecting this command *before* giving it to > drbdsetup-83. > > Regards, > > Brian. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed