Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Thank you for your help , Frank. Actually, we have two drbd partition A using device /dev/vg01/share and partition B /dev/vg02/share, we also have two system Business A with partition A and Business B with partition B on the machine. In our design, we take A-A, B-B, when using this mode, config is right. But someone take A-B mode, the peer's device is wrong in configuration file. But everything is ok, A can sync to B, and with heartbeat every node can take-over, I am worrying about some risksabout drbd in the future . (DRBD configuring is automated.) Can you explain it to me?
Thank you!
在 2012-05-21 15:24:22，"Felix Frank" <ff at mpexnet.de> 写道：
>Hi,
>
>On 05/21/2012 04:12 AM, 陈楠 wrote:
>> 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.
>
>please just paste the config just as Dan specified to *both* nodes. That
>should work.
>
>The idea with the DRBD configs is to tell each node about the whole
>picture, and each node will pick the information it needs. That's why it
>can even work when each node sees a slightly different picture.
>But don't try tricking DRBD, because you will only confuse yourself.
>Just install the whole, working config on each of your nodes.
>
>HTH,
>Felix
>
>> At 2012-05-18 19:00:24,"Dan Barker" <dbarker at visioncomm.net
>> <mailto: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;
>>
>> }
>>
>> }
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120521/578d7ea1/attachment.htm>