Hi.
I've been trying to find some way to change the protocol of a DRBD device,
and have been getting stuck every time:
r...@xen-80-31-00:/etc/xen/guests# drbdadm disconnect build-hardy-x64-root
r...@xen-80-31-00:/etc/xen/guests# drbdadm adjust build-hardy-x64-root
22: Failure: (139) Protocol C required
Command 'drbdsetup 22 net 10.99.99.200:7722 10.99.99.100:7722 A
--set-defaults --create-device --allow-two-primaries' terminated with exit
code 10
r...@xen-80-31-00:/etc/xen/guests# drbdadm down build-hardy-x64-data
r...@xen-80-31-00:/etc/xen/guests# drbdadm down build-hardy-x64-root
r...@xen-80-31-00:/etc/xen/guests# drbdadm adjust build-hardy-x64-root
22: Failure: (139) Protocol C required
Command 'drbdsetup 22 net 10.99.99.200:7722 10.99.99.100:7722 A
--set-defaults --create-device --allow-two-primaries' terminated with exit
code 10
>From drbd.conf:
resource build-hardy-x64-root {
device /dev/drbd22;
disk /dev/datavg/build-hardy-x64-root;
meta-disk /dev/datavg/drbd_log[22];
protocol A;
on xen-80-31-00 {
address 10.99.99.200:7722;
}
on xen-33-18-02 {
address 10.99.99.100:7722;
}
}
resource build-hardy-x64-data {
device /dev/drbd23;
disk /dev/datavg/build-hardy-x64-data;
meta-disk /dev/datavg/drbd_log[23];
protocol A;
on xen-80-31-00 {
address 10.99.99.200:7723;
}
on xen-33-18-02 {
address 10.99.99.100:7723;
}
}
.....
The other node is not online at this time, so it shouldn't be confusing the
primary node, should it?
Anything else I can do short of rebooting the server (which would be
seriously service affecting)?
--Sam
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
