[OpenAFS] clarification on client caches

Derrick J Brashear shadow@dementia.org
Tue, 7 Sep 2004 15:33:58 -0400 (EDT)

On Tue, 7 Sep 2004, Wes Chow wrote:

>> the "-files 50000" option.  If I start it out at the cache size I want
>> (30 gigs), accesses to /afs hang without afs_cachetrim running amok.
>> However, if I lower the cache size it seems to work.  Starting at a
>> lower cache size and resizing upwards doesn't seem to help.
> The plot thickens...  a CentOS client (a rebuild of Redhat Enterprise
> 3) can create a client cache of 50 gigs fine.  A Debian client with
> the same size cache and same options to afsd seg faults.  Both were
> using MEDIUM parameters.

so what's different:

> Also, does it matter which gcc was used in compiling the kernel?  The
> Debian client is using a custom compiled 2.4.27 kernel with gcc 3.3.
> The Centos kernel is 2.4.21-9.0.1.EL.c0smp.  I don't know which
> compiler it was built with.

it shouldn't, as long as the afs module is built with the same one. it 
wouldn't be inconceivable for an optimizer bug to exist, but none has 
previously shown up at least recently.