Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
We just setup a drbd (drbd84-8.9.3) in CentOS 7. When we start drbd, always
get "Wrong medium type" logs. Would like to have your opinions and
suggestions for this issue.
Before I send this email, I have made many trys including re-create drbd,
set as primary. We always see "Wrong medium type" logs.
Thanks very much. Caigen
Here is detailed logs:
Sep 16 12:08:46 mill-mirr systemd: Starting DRBD -- please disable. Unless
you are NOT using a cluster manager....
Sep 16 12:08:46 mill-mirr drbd: Starting DRBD resources: [
Sep 16 12:08:46 mill-mirr drbd: create res: export
Sep 16 12:08:46 mill-mirr systemd-udevd: error: /dev/drbd0: Wrong medium
type
Sep 16 12:08:46 mill-mirr drbd: prepare disk: export
Sep 16 12:08:46 mill-mirr systemd-udevd: error: /dev/drbd1: Wrong medium
type
Sep 16 12:08:46 mill-mirr systemd-udevd: error: /dev/drbd0: Wrong medium
type
Sep 16 12:08:46 mill-mirr drbd: adjust disk: export
Sep 16 12:08:46 mill-mirr systemd-udevd: error: /dev/drbd1: Wrong medium
type
Sep 16 12:08:46 mill-mirr drbd: adjust net: export
Sep 16 12:08:46 mill-mirr drbd: ]
Sep 16 12:08:46 mill-mirr drbd: WARN: stdin/stdout is not a TTY; using
/dev/consoledegr-wfc-timeout has to be shorter than wfc-timeout
Sep 16 12:08:46 mill-mirr drbd: degr-wfc-timeout implicitly set to
wfc-timeout (5s)
Sep 16 12:08:46 mill-mirr drbd: outdated-wfc-timeout has to be shorter than
degr-wfc-timeout
Sep 16 12:08:46 mill-mirr drbd: outdated-wfc-timeout implicitly set to
degr-wfc-timeout (5s)
Sep 16 12:08:46 mill-mirr drbd: degr-wfc-timeout has to be shorter than
wfc-timeout
Sep 16 12:08:46 mill-mirr drbd: degr-wfc-timeout implicitly set to
wfc-timeout (5s)
Sep 16 12:08:46 mill-mirr drbd: outdated-wfc-timeout has to be shorter than
degr-wfc-timeout
Sep 16 12:08:46 mill-mirr drbd: outdated-wfc-timeout implicitly set to
degr-wfc-timeout (5s)
Sep 16 12:08:51 mill-mirr drbd: .
Sep 16 12:08:51 mill-mirr systemd: Started DRBD -- please disable. Unless
you are NOT using a cluster manager..
Our configuration is:
# more export.res
resource export {
volume 0 {
device /dev/drbd0;
disk /dev/sda2;
meta-disk internal;
}
volume 1 {
device /dev/drbd1;
disk /dev/sda3;
meta-disk internal;
}
on mill-pri {
address 10.0.1.146:7788;
}
on mill-mirr {
address 10.0.1.1:7788;
}
}
# more global_common.conf
common {
handlers {
pri-on-incon-degr
"/usr/lib/drbd/notify-pri-on-incon-degr.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /pro
c/sysrq-trigger ; reboot -f";
pri-lost-after-sb
"/usr/lib/drbd/notify-pri-lost-after-sb.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /pro
c/sysrq-trigger ; reboot -f";
local-io-error "/usr/lib/drbd/notify-io-error.sh;
/usr/lib/drbd/notify-emergency-shutdown.sh; echo o > /proc/sysrq-tr
igger ; halt -f";
}
startup {
wfc-timeout 5;
become-primary-on mill-pri;
}
net {
protocol C;
}
syncer {
rate 25M;
verify-alg md5;
}
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20160916/c0d29918/attachment.htm>