Package: drbd-utils Version: 8.9.2~rc1-2 Severity: normal Tags: upstream Hi,
documentation for drbdadm new-current-uuid suggests it should take a resource as argument, in common with most other drbdadm commands. But actually, it only accepts volume numbers: root@ophon:~# drbdadm -- --clear-bitmap new-current-uuid mcvtest new-current-uuid requires a specific volume id, but none is specified. Try 'new-current-uuid minor-<minor_number>' or 'new-current-uuid mcvtest/<vnr>' So you have to say minor-5 (if, say, we're dealing with /dev/drbd5). I think this is a bug (it should accept the resource name like the other drbdadm commands do), but at the very least it should be more clearly documented. Regards, Matthew -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (990, 'stable'), (990, 'oldstable'), (500, 'oldstable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
