Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I have experienced this situation while running drbd-0.7.18. The only
way have have been able to clear this error was to take the hit and
invalidate the secondary host (thus resyning the entire secondary
drive). If anyone else has any ideas I would be interested as well.
-Chris
Fabio Silva wrote:
>
> My drbd.conf - the same in both nodes
> ---------------------------------------------------------
> resource r0 {
> protocol C;
> incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ;
> halt -f";
>
> startup {
> # wfc-timeout 0;
> degr-wfc-timeout 120; # 2 minutes.
> }
>
> disk {
> on-io-error panic;
> }
>
> 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)
> # max-buffers 2048;
> # max-epoch-size 2048;
> # ko-count 4;
> on-disconnect reconnect;
> }
>
> syncer {
> rate 100M;
> group 1;
> #al-extents 257;
> }
>
> on ha-cluster1 {
> device /dev/drbd0;
> disk /dev/sda8;
> address 10.0.1.1:7788 <http://10.0.1.1:7788>;
> meta-disk internal;
> }
>
> on ha-cluster2 {
> device /dev/drbd0;
> disk /dev/sda6;
> address 10.0.1.2:7788 <http://10.0.1.2:7788>;
> meta-disk internal;
> }
> }
> ---------------------------------------------------------
>
>
>
>
> On 9/12/06, *Christopher Harrison* < charrison at inoc.com
> <mailto:charrison at inoc.com>> wrote:
>
> What connect protocol are you using A,B or C. Please send your
> drbd.conf.
> -Chris
>
> Fabio Silva wrote:
> > Hi all, im with a problem with my drbd...
> > when the node A crash, node B is active... but, when the Node A
> > returns, its dont sync, and i can see in the logs like this...
> >
> > Sep 12 09:55:37 ha-cluster2 kernel: drbd0: drbd0_receiver [6673]:
> > cstate WFConnection --> WFReportParams
> > Sep 12 09:55:37 ha-cluster2 kernel: drbd0: Handshake successful:
> DRBD
> > Network Protocol version 74
> > Sep 12 09:55:37 ha-cluster2 kernel: drbd0: incompatible states (both
> > Primary!)
> > Sep 12 09:55:37 ha-cluster2 kernel: drbd0: drbd0_receiver [6673]:
> > cstate WFReportParams --> StandAlone
> > Sep 12 09:55:37 ha-cluster2 kernel: drbd0: error receiving
> > ReportParams, l: 72!
> > Sep 12 09:55:37 ha-cluster2 kernel: drbd0: worker terminated
> > Sep 12 09:55:37 ha-cluster2 kernel: drbd0: asender terminated
> > Sep 12 09:55:37 ha-cluster2 kernel: drbd0: drbd0_receiver [6673]:
> > cstate StandAlone --> StandAlone
> > Sep 12 09:55:37 ha-cluster2 kernel: drbd0: Connection lost.
> > Sep 12 09:55:37 ha-cluster2 kernel: drbd0: receiver terminated
> >
> > ??
> > Why its happend? i've set that this machine is secondary with
> "drbdadm
> > secondary all" and the ha-cluster1 is the primary, but what
> could be ??
> >
> >
> > Regars
> >
> > Fabio
> >
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > drbd-user mailing list
> > drbd-user at lists.linbit.com <mailto:drbd-user at lists.linbit.com>
> > http://lists.linbit.com/mailman/listinfo/drbd-user
> >
>
>
>
>
>
>
> --
> Fabio S. Silva
> LPIC-1 Linux Professional Institute Certified
-------------- next part --------------
A non-text attachment was scrubbed...
Name: charrison.vcf
Type: text/x-vcard
Size: 243 bytes
Desc: not available
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20060912/b3069346/attachment.vcf>