[OpenAFS] many packet are as rx_ignoreAckedPacket and meltdown
Fri, 06 Oct 2006 17:47:02 +0200
-----BEGIN PGP SIGNED MESSAGE-----
Robert Banz wrote:
>>> First, upgrade your fileserver an actual "production" release, such
>>> as 1.4.1. 1.3.81 was pretty good, but, not without problems. (1.4.1
>>> is not without problems, but with less.)
>> We are thinking of that as a one (last) of possibility, but we are
>> running tens of linux (Debian/stable) servers (not only AFS) as a part
>> of our distributed computing environment and we are trying to keep our
>> server configuration as close as possible to stable dist. And short
>> summary: we don't have any significant AFS problems with same
>> configuration for 1+years...
> Keeping with "random linux distro's" idea of stable for your AFS code i=
> not a good idea. Stick with OpenAFS's idea of stable -- and while for
> short periods I've ran "development" (e.g late 1.3.*) code on my
> production AFS servers when I was in a pinch, stick to the production
> releases. Ignore what Debian thinks, because they don't know what
> they're talking about ;)
The problem is, OpenAFS isn=B4t synced with distros developement.
OpenAFS got better and better on a very quick timeslot (a BIG thx for
all the team behind this). So far it wasn=B4t easy for the "stable"
distros to select the correct version to take. At least in sarge it=B4s a
problem, because sarge is stable for some time...
In next Debian there will be a 1.4.x version. And I think the 1.4.1+
versions are much stable than 1.3.8x and so better to keep stable for
At least there ARE some 1.4.x builts of OpenAFS for debian sarge easy to
Nevertheless we use 1.4.1 and 1.4.fc2/4 in production here on debian
sarge and it works well enough for our small cell.
Most of our "problems" are with the windows version, which is not as
mature as the linux version (in my opinion), which doesn=B4t mean it isn=B4=
as stable as the linux version.
TU Graz, Institut f=FCr ComputerGraphik & WissensVisualisierung
Tel: +43 316 873-5405 E-Mail: firstname.lastname@example.org
Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
-----END PGP SIGNATURE-----