[OpenAFS] clarification on client caches

[Dexter 'Kim' Kimball]

> 
>> then seems to work. I never see afs_cachetrim appear in top 
> (though my delay is set low), and the machine seems usable.
> 

May have been covered elsewhere in thread and if so oh well:  are you
filling the cache until it purges?  I.e. did you initialize a 50 GB
cache (in which case a huge number of Vfiles are created and you have to
be careful, at the least, with # of inodes on cache partition); or, did
you initialize and 50 GB cache and write into it until the cache begins
to purge?

Things may have changed radically since I last tried to use large (12GB)
caches several years ago -- what I found then was this:  cache
initialization was fine; cache purging, however, consumed all of the AFS
client resources and the client stopped responding to user requests.
The client appeared to be hung, but using afsmonitor to check cache
activity I could see that the purging was taking place during the
"freeze" times.

Dropped back to a 3GB cache which worked fine.

If you've fully populated a 50GB cache and the consequent cache purging
doesn't cause the AFS client to go catatonic, I'd be very interested in
knowing.

Thx.

Kim


=================================
Kim (Dexter) Kimball
CCRE, Inc.
kim<dot>kimball<at>jpl.nasa.gov
dhk<at>ccre.com





> I'll try a couple more variations to see if I can get more
> specific information.
> 
> 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.
> 
> Wes
> 
> -- 
> http://www.woahnelly.net/~wes/          OpenPGP key = 0xA5CA6644
> fingerprint = FDE5 21D8 9D8B 386F 128F  DF52 3F52 D582 A5CA
> 6644 _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org 
> https://lists.openafs.org/mailman/listinfo/openafs-info
>