Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Felix,
Thaks for the info and sorry for the late response I had a week off for the
holidays. When I try to manually establish the connection between the
nodes, not via heartbeat, I get the following state:
# modprobe drbd
[root at cpvmdc1 conf.d]# drbdadm up r0
[root at cpvmdc1 conf.d]# drbdadm primary r0
[root at cpvmdc1 conf.d]# cat /proc/drbd
version: 8.4.0 (api:1/proto:86-100)
GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by root at cpvmdc1,
2011-12-21 17:13:05
0: cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown C r----s
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:200736
Now, I can see the node listening on port 7788:
[root at cpvmdc1 private]# netstat -tuplen | grep 7788
tcp 0 0 192.168.1.100:7788 0.0.0.0:*
LISTEN 0 290311 -
On the secondary:
[root at cpvmdc2 ~]# modprobe drbd
[root at cpvmdc2 ~]# drbdadm up r0
[root at cpvmdc2 ~]# cat /proc/drbd
version: 8.4.0 (api:1/proto:86-100)
GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by root at cpvmdc1,
2011-12-21 17:13:05
0: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----s
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:200736
[root at cpvmdc2 ~]# drbdadm connect r0
[root at cpvmdc2 ~]# cat /proc/drbd
version: 8.4.0 (api:1/proto:86-100)
GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by root at cpvmdc1,
2011-12-21 17:13:05
0: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----s
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:200736
but after the "connect" command on the secondary node, the node stays in
StandAlone and I can't see port 7788 open on it. Also the connection state
of the primary changes from WFConnection to StandAlone:
[root at cpvmdc1 conf.d]# cat /proc/drbd
version: 8.4.0 (api:1/proto:86-100)
GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by root at cpvmdc1,
2011-12-21 17:13:05
0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s
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:200736
and it gives up trying to connect.
My drbd resource config file looks like this now:
[root at cpvmdc1 conf.d]# cat /etc/drbd.d/r0.res
resource r0 {
meta-disk internal;
device minor 0;
net {
protocol C;
}
disk { on-io-error detach; }
syncer {
rate 100M;
verify-alg md5;
}
on cpvmdc1 {
device /dev/drbd0;
address 192.168.1.100:7788;
disk /dev/sdc1;
meta-disk internal;
}
on cpvmdc2 {
device /dev/drbd0;
address 192.168.1.101:7788;
disk /dev/sdc1;
meta-disk internal;
}
}
When I run the "syncer" option for drbdadm I get:
[root at cpvmdc1 conf.d]# drbdadm syncer r0
drbdadm: Unknown command 'syncer'
Am I still missing somethinfg?
Thanks again for your help
Igor
On Fri, Dec 23, 2011 at 7:27 PM, Felix Frank <ff at mpexnet.de> wrote:
> Hi,
>
> On 12/23/2011 03:37 AM, Igor Cicimov wrote:
> > Thanks to both of you guys for your help. Now the error is gone but they
> > are still in StandAlone mode instead of connected:
>
> did you start DRBD by initscript? Looks as though you used "drbdadm
> attach" on each node. Don't do that.
> You should use "drbdadm up" to activate a resource.
>
> Now that the disks are already attached, you can just do
> "drbdadm syncer" then "drbdadm connect", on each node respectively.
>
> > It's also strange
> > that I'm sure I formated drbd partition with ext3 but is showing as ext2
> > in mount:
>
> Ext3 is downwards compatible. You can mount ext3 partitions as ext2, and
> your kernel will refrain from using the ext3 journal.
>
> Is there an fstab entry for drbd0? Does it specify ext2 as filesystem?
> Or did you mount that manually?
>
> Either way, just be sure that mount knows the FS is supposed to have a
> journal, and this should Just Work.
>
> HTH,
> Felix
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120103/d2f44d75/attachment.htm>