Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
What would you expect? You used _dry-run_ command only. It is used just to
check if your configuration is OK.
Try to execute it without -d switch, or restart DRBD service.
2009/2/27 LLLActive at GMX.Net <LLLActive at gmx.net>
> Hi all,
>
> I set up a DRBD with SLES 10 SP2. They do not sync yet.
>
> Testing, I used the dry-run command:
>
> drbdadm -d adjust all
>
> Result:
> drbdadm -d adjust all
> drbdsetup /dev/drbd0 syncer --set-defaults --create-device --rate=700000
> --al-extents=257
> drbdsetup /dev/drbd0 net 10.9.8.4:7788 10.9.8.3:7788 C --set-defaults
> --create-device
>
> _Setup_
>
> -= Primary =-
>
> _on Primary the drbd.conf_:
> on SLE104 {
> device /dev/drbd0;
> disk /dev/sdb1;
> address 10.9.8.4:7788;
> meta-disk internal;
> }
>
> on SLE103 {
> device /dev/drbd0;
> disk /dev/sdb1;
> address 10.9.8.3:7788;
> meta-disk internal;
> }
>
>
> version: 8.3.0 (api:88/proto:86-89)
> GIT-hash: 9ba8b93e24d842f0dd3fb1f9b90e8348ddb95829 build by
> root at SLE10-CLU2-AWS3, 2009-01-22 14:08:02
> 0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r---
> ns:0 nr:0 dw:805193092 dr:1759248760 al:357623 bm:357533 lo:0 pe:0 ua:0
> ap:0 ep:1 wo:b oos:1465107312
>
> =- END Primary -=
>
> -= Secondary =-
> drbdadm -d adjust all
> drbdsetup /dev/drbd0 syncer --set-defaults --create-device --rate=700000
> --al-extents=257
>
>
> _on Secondary the drbd.conf_:
> on SLE104 {
> device /dev/drbd0;
> disk /dev/sdb1;
> address 10.9.8.4:7788;
> meta-disk internal;
> }
>
> on SLE103 {
> device /dev/drbd0;
> disk /dev/sdb1;
> address 10.9.8.3:7788;
> meta-disk internal;
> }
>
> version: 8.3.0 (api:88/proto:86-89)
> GIT-hash: 9ba8b93e24d842f0dd3fb1f9b90e8348ddb95829 build by
> root at SLE10-CLU2-AWS3, 2009-02-19 14:33:19
> 0: cs:WFConnection ro:Secondary/Unknown ds:Inconsistent/DUnknown C r---
> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
> oos:1465107312
>
> netstat -tnlp does not show the ports listening (on both):
>
> Proto Recv-Q Send-Q Local Address Foreign Address State
> PID/Program name
> tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN
> -
> tcp 0 0 0.0.0.0:5989 0.0.0.0:* LISTEN
> 3543/owcimomd
> tcp 0 0 0.0.0.0:711 0.0.0.0:* LISTEN
> 10287/rpc.mountd
> tcp 0 0 0.0.0.0:5801 0.0.0.0:* LISTEN
> 3836/xinetd
> tcp 0 0 0.0.0.0:37193 0.0.0.0:* LISTEN
> -
> tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
> 10090/smbd
> tcp 0 0 10.9.8.4:427 0.0.0.0:* LISTEN
> 3427/slpd
> tcp 0 0 127.0.0.1:427 0.0.0.0:* LISTEN
> 3427/slpd
> tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN
> 3836/xinetd
> tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
> 3428/portmap
> tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN
> 3596/cupsd
> tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
> 3883/master
> tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN
> 10090/smbd
> tcp 0 0 :::22 :::* LISTEN
> 3731/sshd
> tcp 0 0 ::1:25 :::* LISTEN
> 3883/master
>
> =- END Secondary -=
>
> SuSEfirewall2 is used on both, with the ports 7788:7799 open on internal
> zone, where the NIC's are connected via crossover cable.
>
> I do not know if it matters, but the Secondary has an older Kernel than
> Primary:
> Primary : 2.6.16.60-0.33-default #1 Fri Oct 31 14:24:07 UTC 2008 x86_64
> x86_64 x86_64 GNU/Linux
> Secondary: 2.6.16.60-0.34-default #1 Fri Jan 16 14:59:01 UTC 2009 x86_64
> x86_64 x86_64 GNU/Linux
>
> DRBD was compiled with their current Kernels on both separately.
>
> Before I actually do a "drbdadm adjust all", is the config above sound? It
> does not seem right according to the messages.
>
> TIA
>
> :-)
> Al
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090227/b778b5a0/attachment.htm>