Bart Coninckx wrote:
On Sunday 06 June 2010 12:18:48 Olivier Le Cam wrote:
Bart Coninckx wrote:
Is it the normal behaviour? My guess is that node1 could not gain again
the Primary role before its data is UpToDate...
Thanks in anticipation for your comments.
Best regards,
Sounds like a Heartbeat issue. Heartbeat should not make the node primary
before the sync has finished. What resource agent did you use?
OK, that confirm my though, thank you Bart. I probably missed to
configure something!
My haresources file only has this in:
drbd1 IPaddr::192.168.19.125/24/eth1 \
drbddisk::r0 \
Filesystem::/dev/drbd0::/nfs3-exports::ext3::noatime \
killnfsd \
nfs-kernel-server
and what does your drbd.conf look like?
Here it is:
global {
usage-count yes;
}
common {
protocol C;
handlers {
pri-on-incon-degr "echo o >/proc/sysrq-trigger ; halt -f";
pri-lost-after-sb "echo o >/proc/sysrq-trigger ; halt -f";
local-io-error "echo o >/proc/sysrq-trigger ; halt -f";
}
startup {
degr-wfc-timeout 120; # 2 minutes.
}
disk {
on-io-error detach;
}
net {
}
syncer {
rate 33M;
al-extents 257;
}
}
resource r0 {
on drbd1 {
device /dev/drbd0;
disk /dev/vg1/storage;
address 192.168.19.123:7789;
meta-disk internal;
}
on drbd2 {
device /dev/drbd0;
disk /dev/vg1/storage;
address 192.168.19.124:7789;
meta-disk internal;
}
}
--
Olivier
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
