[OpenAFS] OpenAFS 1.6.5 Linux client cache sizes

[Robert Milkowski]

It currently pre-allocates some files in the cache and/or checks that they
are already there, and also it currently happens serially from a single
thread.

Ideally afsd should be able to dynamically create files when needed and
avoid pre-allocating them during start up.


Best regards,
 Robert Milkowski


> -----Original Message-----
> From: openafs-info-admin@openafs.org [mailto:openafs-info-
> admin@openafs.org] On Behalf Of Volkmar Glauche
> Sent: 08 January 2015 14:20
> To: openafs-info
> Subject: [OpenAFS] OpenAFS 1.6.5 Linux client cache sizes
> 
> Dear all,
> 
> we are running OpenAFS clients with up to 1TB space available for cache
> partitions. These are multiuser cluster nodes where cache space should
> be as large as possible. Until now, there was (inadvertently) a limit
> of ~200GB set to the cache size by restrictive afsd options.
> I now removed most of these options, my current command line for afsd
> looks like
> 
> /usr/bin/afsd -chunksize 30 -fakestat -blocks <SPACE_ON_DEVICE>
> 
> Now it takes a very long time (~hours) to start up afsd, in some cases
> the afs cache scan even fails with a kernel panic. Is there any way to
> make efficient use of ~1TB cache partitions?
> 
> Volkmar
> 
> --
> Freiburg Brain Imaging
> http://fbi.uniklinik-freiburg.de/
> Tel. +761 270-54783
> Fax. +761 270-54819
> 
> 
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info