Hello again, 

I now tried reinstalling 8.2.1 and installing an older version (didn't find a 
0.7 built for my kernel) so I took 8.0.4.

Same behaviour :-/

I can promote it by hand.....then crm_mon shows DRBD as unmanaged, after that 
demoting it again and it comes up managed by heartbeat just fine -.-

Dominik: Are there rpms for the 8.2.5-version (except the ones commercially 
published by linbit) for my kernel 2.6.18-8.el5?

I'm definitely not familiar with compiling myself (I read something about that 
kernel and drbd-kernel-module need be compiled with the same version of 
gcc..this doesn't make things easier-.-)  or upgrading kernel...so I'm a little 
afraid of doing this...

Regards
Florian

> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> ha.org] Im Auftrag von Dominik Klein
> Gesendet: Montag, 10. März 2008 16:43
> An: General Linux-HA mailing list
> Betreff: Re: AW: AW: AW: [Linux-HA] Switchover problem with DRBD
> 
> Schmidt, Florian wrote:
> > Hello again,
> >
> > you're right, i do have DRBD 8.2.1 installed.
> >
> > Well, you mean downgrading on 0.7.x would be better?
> > This is only a test-cluster so this shouldn't be a problem. But I'll try 
> > re-installing
> my current DRBD-version first and then (if this doesn't help) downgrading to 
> 0.7.x-
> DRBD.
> 
> I guess upgrading to 8.2.5 would be the way to go. Although I'm not sure
> the issue you had was fixed in that version, a downgrade to 0.7 should
> never be needed.
> 
> I sometimes saw what you reported (no response from drbd module) during
> my own tests, but I was not able to reproduce it. Sorry.
> 
> Regards
> Dominik
> _______________________________________________
> 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

Reply via email to