[OpenAFS] All limitations of OpenAFS
Tue, 26 Jan 2010 15:12:38 -0500
On Tue, Jan 26, 2010 at 7:49 AM, Lars Schimmer <email@example.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> For a new EU project we want to setup a OpenAFS cell.
> As we could hit some limitations of OpenAFS, I would like to collect all
> known limitations of current OpenAFS systems (1.5.70 on windows and
> 1.4.11 on linux that is).
> I know of:
> - -one RW copy of a volume
> - -max 6 RO copies from one volume
Are you referring to the number of repsites that can be represented in
the vldb, or the number of distinct clones supported within a volume
repsites: IIRC, vldb version 4 supports 13 repsites (so a max of 12
RO sites w/o BK; 11 w/ a BK repsite)
clones: This depends on whether your backing store is namei or inode.
For namei, the safe limit is five volumes within a volume group.
Thus, in the typical case you get one RW and four clones. Note that
you can go beyond this limit (IIRC the true limit is 35), but there
must be DV overlap for every vnode (or clone operations will fail) --
each vnode (irrespective of differences in uniquifier) on namei can
have at most five divergent versions at any given point in time.