Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
When I have not configure peer node, drbd service ask me to configure peer, when I configure peer node, these keywords must be configured. I think ip address meta disk of peer node is useful, but the device of peer node is useless in configuration file, right?
[root at IVE151 ~]# service drbd start
/etc/drbd.d/r0.res:8: in resource r0, on IVE150 { ... }: 'disk' keyword missing.
/etc/drbd.d/r0.res:8: in resource r0, on IVE150 { ... }: 'meta-disk' keyword missing.
Starting DRBD resources: /etc/drbd.d/r0.res:8: in resource r0, on IVE150 { ... }: 'disk' keyword missing.
/etc/drbd.d/r0.res:8: in resource r0, on IVE150 { ... }: 'meta-disk' keyword missing.
/etc/drbd.d/r0.res:8: in resource r0, on IVE150 { ... }: 'disk' keyword missing.
/etc/drbd.d/r0.res:8: in resource r0, on IVE150 { ... }: 'meta-disk' keyword missing.
At 2012-05-21 10:03:24,"陈楠" <chennan.1986 at 163.com> wrote:
HI Dan,
My drbd version is 8.3.11. I configure Host A like you say.
[root at IVE151 ~]# cat /etc/drbd.d/r0.res
resource r0 {
on IVE151 {
device /dev/drbd0;
disk /dev/vg01/share;
address 2.2.2.151:7788;
meta-disk internal;
}
}
I have create meta-data successfully. Then I start drbd service , I got this message.
[root at IVE151 ~]# service drbd start
Starting DRBD resources: /etc/drbd.d/r0.res:1: in resource r0:
Missing section 'on <PEER> { ... }'.
resource r0: cannot change network config without knowing my peer.
[ d(r0) s(r0) ].
[root at IVE151 ~]# service drbd status
drbd driver loaded OK; device status:
version: 8.3.11 (api:88/proto:86-96)
GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root at node1, 2011-08-30 19:38:51
m:res cs ro ds p mounted fstype
0:r0 StandAlone Secondary/Unknown Inconsistent/DUnknown r----s
This message shows that I cannot start drbd successfully. I think that you must configure peer node include node name, ip address, then you can start drbd service, right?
At 2012-05-18 22:21:26,"陈楠" <chennan.1986 at 163.com> wrote:
You mean that drbd server like Host A just care the configuration about itself, right? I'll try it later. Thank you!
At 2012-05-18 19:00:24,"Dan Barker" <dbarker at visioncomm.net> wrote:
The configurations SHOULD match to simplify maintenance, but server A will completely ignore server B settings, and server B will completely ignore server A settings. Your config is being read by the servers as:
Host A:
resource r0 {
on ME {
device /dev/drbd0;
disk /dev/vg01/share;
address 2.2.2.150:7788;
meta-disk internal;
}
}
and Host B is like this:
resource r0 {
on ME {
device /dev/drbd0;
disk /dev/vg02/share;
address 2.2.2.151:7788;
meta-disk internal;
}
}
Which is (I believe) what you wanted.
Dan
From:drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of ??
Sent: Friday, May 18, 2012 3:20 AM
To: drbd-user
Subject: [DRBD-user] drbd wrong lower device doubt
Hi All, I have some doubts about drbd. I have configure two servers as Host A and Host B. Host A drbd configuration is like this:
resource r0 {
on A {
device /dev/drbd0;
disk /dev/vg01/share;
address 2.2.2.150:7788;
meta-disk internal;
}
on B {
device /dev/drbd0;
disk /dev/vg01/share;
address 2.2.2.151:7788;
meta-disk internal;
}
}
and Host B is like this:
resource r0 {
on A {
device /dev/drbd0;
disk /dev/vg02/share;
address 2.2.2.150:7788;
meta-disk internal;
}
on B {
device /dev/drbd0;
disk /dev/vg02/share;
address 2.2.2.151:7788;
meta-disk internal;
}
}
You can notice that Host A and Host B configuration file is not same. Actually Host A lower device is /dev/vg01/share and Host B lower device is /dev/vg02/share. The specified destination lower device is wrong in each server. Network setting is right . I set Host A disk state to UpToDate and Host B disk state inconsistent. I find that Host A is syncing to Host B. Why it can work regularly when I configure wrong lower device.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120521/7fc07d76/attachment.htm>