<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi all,<br>
<br>
Previously we've been using DRBD kernel 8.4.3 and userland tools
8.4.3.<br>
<br>
We've just loaded a new mirror pair with kernel module version 8.4.6
and tools 8.9.2.<br>
<br>
However, some things have broken because the create /dev/ device
name is not matching what is expected - here is an example config:<br>
<br>
resource drbd0061 {<br>
protocol C;<br>
net {<br>
allow-two-primaries;<br>
}<br>
disk {<br>
on-io-error detach;<br>
}<br>
on machine1 {<br>
device /dev/drbd0061;<br>
disk /dev/vg_ssd/vol0061;<br>
address 10.0.0.6:7001;<br>
meta-disk internal;<br>
}<br>
on machine2 {<br>
device /dev/drbd0061;<br>
disk /dev/vg_ssd/vol0061;<br>
address 10.0.0.7:7001;<br>
meta-disk internal;<br>
}<br>
}<br>
<br>
<br>
This used to create a device:<br>
<br>
/dev/drbd0061<br>
<br>
However, the device now created is:<br>
<br>
/dev/drbd61<br>
<br>
without the leading 0s in the number, on the primary machine.<br>
<br>
This therefore breaks other associations which expect
"/dev/drbd0061" in entirety to be present.<br>
<br>
I can't find any mention of this as a change in the release notes.
It's almost as if it's not recognising my desired configured device
name (and defaulting to another minor), or using a sprintf now
formatting using a %d rather than %s for the device name.<br>
<br>
<br>
Is there a specific problem with my configuration, was there a
planned change in the source, or is this a bug introduced?<br>
<br>
<br>
Thanks in advance for any input.<br>
<br>
Charles.<br>
<div class="moz-signature">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
</div>
</body>
</html>