Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Mar 2013 09:23:13 +0100
From:      Damien Fleuriot <ml@my.gd>
To:        "Eugene M. Zheganin" <emz@norma.perm.ru>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   Re: carp regression in 9.1 ?
Message-ID:  <39FC9737-4F34-4978-BDFE-17410CD2E5C4@my.gd>
In-Reply-To: <514594D7.1020202@norma.perm.ru>
References:  <3B04FCB1-D0D4-4BC9-BB15-5221F438738C@my.gd> <514594D7.1020202@norma.perm.ru>

next in thread | previous in thread | raw e-mail | index | archive | help

On 17 Mar 2013, at 11:03, "Eugene M. Zheganin" <emz@norma.perm.ru> wrote:

> Hi.
>=20
> On 14.03.2013 20:47, Fleuriot Damien wrote:
>> I'm experiencing this odd behavior with 9.1 r24791 for amd64.
> You should definitely sit on 8.x until 10.x will become stable, or upgrade=
 to 10.x from 9.x (at least this is what I do).
> Carp is entirely rewritten in 10.x branch. In the same time, in 9.x carp s=
eems to be desperately broken: for example I was experiencing weird panics o=
n boot, weird behaviour, and, when enabling WITNESS, lots of carp-related LO=
Rs. Furthermore, I was completely unable to boot up with a ipv6-enabled carp=
 - I had to initialize it in multiuser with a custom script. All of this doe=
sn't happen on 10.x, which I had to upgrade to. Right now, if we're talking a=
bout carp, my 10.x production works like a charm. 9.x branch just isn't dest=
ined to production. The situation is a bit improved on 9.1, but still I can c=
ompare this release to 4.6 or 5.0.
>=20
> Eugene.
>=20


 I'm afraid I can't afford 10.x, this is for production, although I acknowle=
dge the problems you're faced with.

Regarding 8.x, this is a guest VM running on proxmox 2.3 which doesn't suppo=
rt stock 8.x (need the virtio kernel option, I'll get a thread reference whe=
n I hit work).


So yeah I'm kinda fucked here... ;)=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39FC9737-4F34-4978-BDFE-17410CD2E5C4>