On 04/17/2015 10:02 AM, Volkmar Glauche wrote:
Dear all,
for the sake of completeness, I would like to revive this thread and share some
of my findings. As I wrote below, I intended to make better use of large disks
for AFS cache partitions, but my initial attempts actually made the AFS clients
Dear all,
for the sake of completeness, I would like to revive this thread and
share some of my findings. As I wrote below, I intended to make better
use of large disks for AFS cache partitions, but my initial attempts
actually made the AFS clients unusable for our requirements.
One problem
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 Milk
Hi,
Volkmar Glauche writes:
> 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 b
