[Bug 1314289] Re: [Precise/regression] drbd 8.4.x backport breaks existing clusters

[Vit Herman]

Hello,

AFAICT, the same change broke creating "named" device nodes in /dev via
udev, causing messages like this when running /etc/init.d/drbd reload:

# /etc/init.d/drbd reload
 * Reloading DRBD Configuration
1: Failure: (124) Device is attached to a disk (use detach first)
Command 'drbdsetup-83 1 disk /dev/mapper/MD1-salesnet /dev/mapper/MD1-salesnet internal --set-defaults --create-device' terminated with exit code 10

Running:
# udevadm test /block/drbd1

I get:
...
spawn_read: '/sbin/drbdadm sh-udev minor-1'(err) 'execvp() failed to exec drbdadm-83: No such file or directory'
spawn_wait: '/sbin/drbdadm sh-udev minor-1' [18952] exit with return code 20
udev_event_execute_rules: no node name set, will use kernel supplied name 'drbd1'
udev_node_add: creating device node '/dev/drbd1', devnum=147:1, mode=0660, uid=0, gid=6
...

Giving me only /dev/drbd1, but no /dev/drbd_salesnet (as before) or
/dev/drbd directory. Installing 2:8.4.3-0ubuntu0.12.04.2 fixed the
problem.

Hopefully it's related, I'm posting it up here in case somebody else
gets bitten by it too.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1314289

Title:
  [Precise/regression] drbd 8.4.x backport breaks existing clusters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1314289/+subscriptions