It could be, as when I setup 2 node cluster, it never shut down DRBD
like that, just gave me errors it couldn't start domU on both nodes
but kept DRBD and the FileSystem mounted.
Although I don't understand before I added the configuration for domU
, DRBD and the Filesystem mounts properly as it should, so it kinda
puzzled me, if there is something wrong with DRBD then something new
to learn :)
When I try to get the config running it fails, and shuts down DRBD in
all boxes, so it shows in the end, this is after corosync tries to
start the VPS and it kills everything.
[r...@fa1 ~]# drbd-overview
1:xen1 Unconfigured . . . .
2:xen2 Unconfigured . . . .
[r...@fa1 ~]#
When I start it up (DRBD):
[r...@fa1 ~]# drbd-overview
1:xen1 Connected Secondary/Secondary UpToDate/UpToDate C r----
2:xen2 Connected Secondary/Secondary UpToDate/UpToDate C r----
[r...@fa1 ~]#
[r...@fa1 ~]# drbdadm state all
DRBD module version: 8.3.8
userland version: 8.3.6
you should upgrade your drbd tools!
'drbdadm state' is deprecated, use 'drbdadm role' instead.
Secondary/Secondary
Secondary/Secondary
[r...@fa1 ~]#
[r...@fa1 ~]# cat /etc/drbd.conf
global {
usage-count no;
}
common {
protocol C;
}
resource xen1 {
disk {
fencing resource-only;
}
#net {
# cram-hmac-alg sha1;
# shared-secret "atjeuisl33t";
# allow-two-primaries;
# }
handlers {
fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
}
syncer {
rate 220M;
}
on fa1.atjeu.com {
device /dev/drbd1;
disk /dev/sda4;
address 10.0.1.1:7789;
meta-disk internal;
}
on xen1.atjeu.com {
device /dev/drbd1;
disk /dev/sda4;
address 10.0.1.2:7789;
meta-disk internal;
}
}
resource xen2 {
disk {
fencing resource-only;
}
#net {
# cram-hmac-alg sha1;
# shared-secret "atjeuisl33t";
# allow-two-primaries;
# }
handlers {
fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
}
syncer {
rate 220M;
}
on fa1.atjeu.com {
device /dev/drbd2;
disk /dev/sdb4;
address 10.0.1.1:7790;
meta-disk internal;
}
on xen2.atjeu.com {
device /dev/drbd2;
disk /dev/sda4;
address 10.0.1.3:7789;
meta-disk internal;
}
}
Thanks!
Joe
On Sun, Jun 27, 2010 at 10:03 AM, Greg Woods <[email protected]> wrote:
> On Sun, 2010-06-27 at 07:57 -0700, Joe Shang wrote:
>
>> Jun 27 10:51:49 xen1 lrmd: [3949]: info: RA output:
>> (drbd_xen2:1:probe:stderr) 'xen2' not defined in your config.
>
> This looks like an error in your DRBD configuration. What is in
> drbd.conf? What does "drbd-overview" or "drbdadm state all" show?
>
> --Greg
>
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
