Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello,
... don't forget to post to the group.
On 01/30/2012 01:06 PM, venkatesh prabhu wrote:
> Hi Andreas,
> Thanks for your quick reply.
>
> The solution you provided me solved the problem number 1.
> But still i am facing the error with up command.
> Please help in get rid of that error.
>
> When i run the "drbdadm up r0" it exits with error code 20.
> Device '0' is configured!
>>> Command 'drbdmeta 0 v08 /dev/vg0/drbdmeta flex-external apply-al'
>>> terminated with exit code 20
You don't need to to bring the DRBD device up after running the init
script, that's the responsibility of the script.
You only need to make it Primary manually if you don't want a cluster
manager to do the job.
If you want pacemaker to do this job, deactivate the init script
completely and follow the DRBD users guide on how to integrate DRBD
into your cluster configuration.
Regards,
Andreas
--
Need help with DRBD?
http://www.hastexo.com/now
>
> But still cat /proc/drdb shows that disk is created and it is in
> inconsistent state.
> Then i can promote it to primary and everything works fine.
>
> How can i get rid of the "Device '0' is configured!" error?
>
> Please help me.
>
> Thank You
> Vengatesh Prabhu
>
>
> On Sat, Jan 28, 2012 at 2:19 PM, Andreas Kurz <andreas at hastexo.com> wrote:
>> Hello,
>>
>> On 01/28/2012 01:26 PM, venkatesh prabhu wrote:
>>> Hi,
>>> Please help me solve my issues.
>>> I am trying to bring up DRBD for first time but i am facing following problems.
>>>
>>> 1. when i start the drbd service for first time it says adjust disk failed:
>>> Starting DRBD resources: [
>>> create res: r0
>>> prepare disk: r0
>>> adjust disk: r0:failed(apply-al:20)
>>> adjust net: r0
>>> ]
>>>
>>> 2. Then creation of metadat "drbdadm create-md r0" is success.
>>
>> Do the metadata creation on both nodes before you start the drbd service
>> and the rest should be fine ... and be sure to use 8.4.1 and nod 8.4.0
>> release.
>>
>> Regards,
>> Andreas
>>
>> --
>> Need help with DRBD?
>> http://www.hastexo.com/now
>>
>>>
>>> 3. Then "drbdadm up r0" fails with exit code 1.
>>> drbdadm up r0 r0: Failure: (102) Local address(port) already in use.
>>> Command 'drbdsetup connect r0 ipv4:10.203.230.136:7788
>>> ipv4:10.203.230.135:7788 --shared-secret=DRBD --ping-timeout=5
>>> --ping-int=10 --connect-int=10 --timeout=60 --protocol=C' terminated
>>> with exit code 1
>>>
>>> 4. If the run the same command drbdadm up r0" it fails with exit code 10.
>>> Device '0' is configured!
>>> Command 'drbdmeta 0 v08 /dev/vg0/drbdmeta flex-external apply-al'
>>> terminated with exit code 20
>>>
>>> but still i can promote the resource to primary and the sync happens
>>> properly between two nodes.
>>>
>>> but how can i avoid those errors? please help me.
>>>
>>> my drbd.conf file is provided below.
>>>
>>> global {
>>> usage-count no;
>>> }
>>>
>>> common {
>>>
>>> protocol C;
>>>
>>> startup {
>>> degr-wfc-timeout 3; #3 = 3 sec..
>>>
>>> wfc-timeout 180; # 3 min.
>>> } # end of startup
>>>
>>> handlers {
>>> } # end of handlers
>>>
>>> disk {
>>> on-io-error detach;
>>> } # end of disk
>>>
>>> net {
>>> timeout 60; # 6 seconds (unit = 0.1 seconds)
>>> connect-int 10; # 10 seconds (unit = 1 second)
>>> ping-int 10; # 10 seconds (unit = 1 second)
>>> ping-timeout 5; # 500 ms (unit = 0.1 seconds)
>>> shared-secret "DRBD";
>>> } # end of net
>>> } # end of common
>>>
>>> resource r0{
>>>
>>> syncer {
>>> rate 100M;
>>> }
>>>
>>> on lab1601 {
>>> device /dev/drbd0;
>>> disk /dev/vg0/mirror;
>>> address 10.203.230.135:7788;
>>> meta-disk /dev/vg0/drbdmeta;
>>> }
>>>
>>> on lab1602 {
>>> device /dev/drbd0;
>>> disk /dev/vg0/mirror;
>>> address 10.203.230.136:7788;
>>> meta-disk /dev/vg0/drbdmeta;
>>> }
>>> } #end
>>>
>>>
>>> Thank You
>>> Vengatesh Prabhu
>>>
>>>
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> 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: signature.asc
Type: application/pgp-signature
Size: 222 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120202/8410ada0/attachment.pgp>