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
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
Milkowski
-Original Message-
From: openafs-info-ad...@openafs.org [mailto:openafs-info-
ad...@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
Hi,
Volkmar Glauche volkmar.glau...@uniklinik-freiburg.de 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
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
