Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, Feb 24, 2009 at 11:59:08PM +0200, Theophanis Kontogiannis wrote:
> Good Evening Everyone.
hi.
please avoid html mails on mailing lists.
and try to get your outlook to get the linebreaks right,
and not introduce so many extra blank lines.
good luck ;)
but anyways...
> I have a two node cluster of CentOS 5.
>
> The fencing is based on WTI PDU
>
> I have GFS2 over LVM over DRBD
>
>
>
> DRBD is version 8.2.6
>
> Kernel is version 2.6.18-92.1.10.el5.centos.plus
>
>
>
> I have made the drbd to start as a cluster service (and attached on the
> service of drbd are clvmd, and then gfs2 services).
>
>
>
> Anyway the problem is that I have not managed a single time to make Primary
> on both nodes, all the resources (so the clvmd does not start, and so gfs2
> does not mount and so no clustered service starts).
>
>
>
> This one last time that happened this (and made me post this request for
> help) the status is the following:
>
>
>
> TWEETY1 (node A)
>
> [root at tweety-1 ~]# cat /proc/drbd
> version: 8.2.6 (api:88/proto:86-88)
> GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by
> buildsvn at c5-x8664-build, 2008-08-07 17:44:27
> 0: cs:WFBitMapS st:Secondary/Secondary ds:UpToDate/Outdated C r---
> ns:0 nr:0 dw:0 dr:0 al:0 bm:24 lo:0 pe:0 ua:0 ap:0 oos:126976
ok, this is still resyncing, at least it should be soonish change to
"SyncSource" on this node, and to "SyncTarget" on the other.
if it does not, retry with 8.2.7, or 8.3.0.
> 1: cs:Connected st:Secondary/Secondary ds:UpToDate/UpToDate C r---
> ns:811008 nr:0 dw:0 dr:811008 al:0 bm:192 lo:0 pe:0 ua:0 ap:0 oos:0
and that one is secondary on both sides.
you claim you have not been able to make it Primary.
well, what happens, exactly, if you say "drbdadm primary" ?
> [root at tweety-1 ~]# dmesg|grep drbd
nothing interessting in there.
apart from no hint whatsoever of someone even trying to make it primary.
so it stays secondary.
> TWEETY2 (node B)
>
>
>
> [root at tweety-2 ~]# cat /proc/drbd
>
> version: 8.2.6 (api:88/proto:86-88)
> GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by
> buildsvn at c5-x8664-build, 2008-08-07 17:44:27
> 0: cs:WFBitMapT st:Secondary/Secondary ds:Outdated/UpToDate C r---
> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 oos:126976
> 1: cs:Connected st:Secondary/Secondary ds:UpToDate/UpToDate C r---
> ns:0 nr:811008 dw:811008 dr:0 al:0 bm:96 lo:0 pe:0 ua:0 ap:0 oos:0
[again, kernel log stripped]
> The two nodes are connected back to back with a private GigEth link for the
> DRBD syncing.
>
>
>
> The public network access is done through separate Ethernet interfaces
>
>
>
> The drbd.conf file is
> global {
> usage-count yes;
> }
> common {
> protocol C;
> syncer {
> rate 100M;
> al-extents 257;
> }
> handlers {
> pri-on-incon-degr "echo b > /proc/sysrq-trigger ; reboot -f";
> pri-lost-after-sb "echo b > /proc/sysrq-trigger ; reboot -f";
> local-io-error "echo o > /proc/sysrq-trigger ; halt -f";
> outdate-peer "/sbin/obliterate";
> pri-lost "echo pri-lost. Have a look at the log files. | mail -s 'DRBD
> Alert' root; echo b > /proc/sysrq-trigger ; reboot -f";
> split-brain "echo split-brain. drbdadm -- --discard-my-data connect
> $DRBD_RESOURCE ? | mail -s 'DRBD Alert' root";
> }
> startup {
> wfc-timeout 100;
> degr-wfc-timeout 60; # 1 minutes.
> become-primary-on both;
> }
> disk {
> fencing resource-and-stonith;
> }
> 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)
> max-buffers 2048;
> max-epoch-size 2048;
> ko-count 10;
> allow-two-primaries;
> cram-hmac-alg "sha1";
> shared-secret "*****";
> after-sb-0pri discard-least-changes;
> after-sb-1pri violently-as0p;
> after-sb-2pri violently-as0p;
> rr-conflict call-pri-lost;
> data-integrity-alg "crc32c";
> }
> }
> resource r0 {
> device /dev/drbd0;
> disk /dev/hda4;
> meta-disk internal;
> on tweety-1 { address 10.254.254.253:7788; }
> on tweety-2 { address 10.254.254.254:7788; }
> }
> resource r1 {
> device /dev/drbd1;
> disk /dev/hdb4;
> meta-disk internal;
> on tweety-1 { address 10.254.254.253:7789; }
> on tweety-2 { address 10.254.254.254:7789; }
> }
>
> I would appreciate any help or comments for mistakes I do not see on the
> configuration.
>
> Thank you All for your Time.
>
>
>
> Theophanis Kontogiannis
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
__
please don't Cc me, but send to list -- I'm subscribed