Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi all,
the 4-node replication is working fine and i can mange the resources in
Pacemaker. In the documentation of the user guide i read that's not
possible in Pacemaker 1.05 to create a 4 node cluster only 2. What's the
status of this feature? Is it integrated or in which version is it
planned to integrate this feature?
best regards
Benjamin
Am 17.01.2012 17:31, schrieb Benjamin Knoth:
> Thx a lot Andreas and Jake.
> That was my problem, that all server the stacked config and both
> unstacked configs need.
>
> Now i will create the pacemaker configuration and than everything should
> be ok.
>
> Best regards
>
> Benjamin
>
> Am 17.01.2012 16:33, schrieb Andreas Kurz:
>> Hello,
>>
>> On 01/17/2012 04:22 PM, Benjamin Knoth wrote:
>>> Hello,
>>>
>>> Am 17.01.2012 15:36, schrieb Andreas Kurz:
>>>> On 01/17/2012 03:02 PM, Benjamin Knoth wrote:
>>>>> Hello Andreas,
>>>>>
>>>>> Am 17.01.2012 14:51, schrieb Andreas Kurz:
>>>>>> Hello,
>>>>>>
>>>>>> On 01/16/2012 11:05 AM, Benjamin Knoth wrote:
>>>>>>> Hello,
>>>>>>> i think it's clear and the pacemaker config is also clear but i can't
>>>>>>> get a positiv result.
>>>>>>>
>>>>>>> I started with 4 maschines
>>>>>>>
>>>>>>> vm01 vm02 vm03 vm04
>>>>>>>
>>>>>>> On vm01 and vm02 i created a DRBD resource with this config.
>>>>>>>
>>>>>>> resource test {
>>>>>>> device /dev/drbd3;
>>>>>>> meta-disk internal;
>>>>>>> disk /dev/vg01/test;
>>>>>>> protocol C;
>>>>>>>
>>>>>>>
>>>>>>> syncer{
>>>>>>> rate 800M;
>>>>>>> }
>>>>>>>
>>>>>>> on vm01 {
>>>>>>> address 10.10.255.12:7003;
>>>>>>> }
>>>>>>>
>>>>>>> on vm02 {
>>>>>>> address 10.10.255.13:7003;
>>>>>>> }
>>>>>>> }
>>>>>>>
>>>>>>> On vm03 and vm04 i created this DRBD Resource
>>>>>>>
>>>>>>> resource test2 {
>>>>>>> device /dev/drbd3;
>>>>>>> meta-disk internal;
>>>>>>> disk /dev/vg01/test;
>>>>>>> protocol C;
>>>>>>>
>>>>>>>
>>>>>>> syncer{
>>>>>>> rate 800M;
>>>>>>> }
>>>>>>>
>>>>>>> on vm03 {
>>>>>>> address 10.10.255.14:7003;
>>>>>>> }
>>>>>>>
>>>>>>> on vm04 {
>>>>>>> address 10.10.255.15:7003;
>>>>>>> }
>>>>>>> }
>>>>>>>
>>>>>>> This two unstacked resources are running.
>>>>>>>
>>>>>>> If i look in the documentation i think that i need to create the
>>>>>>> following DRBD Resource on vm01-04.
>>>>>>>
>>>>>>> resource stest {
>>>>>>> protocol A;
>>>>>>> stacked-on-top-of test2 {
>>>>>>> device /dev/drbd13;
>>>>>>> address 10.10.255.16:7009;
>>>>>>> }
>>>>>>> stacked-on-top-of test {
>>>>>>> device /dev/drbd13;
>>>>>>> address 10.10.255.17:7009;
>>>>>>> }
>>>>>>> }
>>>>>>>
>>>>>>> But if i save this and copy them to all vms i get on vm03-04 if i run
>>>>>>> drbdadm --stacked create-md stest
>>>>>>
>>>>>> Use the same, complete config on all nodes.
>>>>> I copied this config on all nodes.
>>>>
>>>> And still not working? Can you provide or pastebin "drbdadm dump all"
>>>> and "cat /proc/drbd" from a node that gives you that error?
>>>
>>> on vm01 and vm02 i get for resource test on cat /proc/drbd. The not
>>> stacked resource works
>>>
>>> 3: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
>>> ns:1077644 nr:0 dw:33232 dr:1044968 al:13 bm:63 lo:0 pe:0 ua:0 ap:0
>>> ep:1 wo:b oos:0
>>>
>>> After i copied the config with resource stest to all 4 nodes i get the
>>> following on vm01 and vm02.
>>>
>>> drbdadm dump all
>>>
>>> drbd.d/stest.res:1: in resource stest, referenced resource 'test2' not
>>> defined.
>>>
>>> And cat /proc/drbd display only the unstacked test resource
>>>
>>> 3: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
>>> ns:0 nr:0 dw:0 dr:528 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
>>>
>>> On vm03 and vm04 i can't also find a stacked resource in /proc/drbd
>>>
>>> 3: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
>>> ns:0 nr:0 dw:0 dr:536 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
>>>
>>> drbdadm dump all
>>> drbd.d/stest.res:1: in resource stest, referenced resource 'test' not
>>> defined.
>>>
>>> You see that on the referenced resource are different between vm01-02
>>> and vm03-04. On the example the unstacked resources had also different
>>> names. In this part DRBD need to know that the referenced resource test
>>> is also available on vm01-02 and test2 is only available on vm03-04.
>>> That is the problem what i need to solve or not?
>>
>> Yes ... put _all_ resource configs on _all_ nodes (and include them in
>> your config of course): the same config on all four nodes
>>
>> Regards,
>> Andreas
>>
>>
>>
>>
>> _______________________________________________
>> drbd-user mailing list
>> drbd-user at lists.linbit.com
>> http://lists.linbit.com/mailman/listinfo/drbd-user
>
>
>
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4520 bytes
Desc: S/MIME Kryptografische Unterschrift
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120118/8b1344f9/attachment.bin>