[OpenAFS] Summary of recommended configuration options from the workshop

Derrick Brashear shadow@gmail.com
Mon, 26 May 2008 21:32:50 -0400

On Mon, May 26, 2008 at 2:49 PM, Christopher D. Clausen
<cclausen@acm.org> wrote:
> Robert Banz <rob@nofocus.org> wrote:
>>> fileserver:
>>> -p 128 ( maximum number of threads )
>>> -vattach # (greater than 1. should this be equal the number of
>>> partitions)
>>> -large
>>> -cb # (1 million or more callbacks)
>>> no fastrestart
>>> more fun options with using demand-attach
>> WHY, pray tell, are we recommending against fastrestart? I think this
>> has been one of the best options in OpenAFS to come along. Is it just
>> a misunderstanding of what it does?
> I use fast-restart as well, although the way to go is demand attach.
> Perhaps this can be pulled into a 1.4.X release candidate for testing?
> Some of us do not want to make the leap to the 1.5.x branch for
> production use.

and so 1.5 will never become stable.

know what's different, server-wise, between 1.4 and 1.5?

it's the part you want backported to 1.4

at which point you have 1.5

so uh... why bother?

> Any downsides of switching from salvager to demand attach?  Affect namei
> or inode fileservers?

see my (2 messages ago)