[OpenAFS] Support for large volumes

[Jeffrey Altman]

Mauro:

No one is working on this at the moment.  The first thing that needs
to be done is to create a list of all of the places in the public
interfaces (wire protocols, pioctls, dump formats, etc) where there
will be an impact as well as local or internal changes.

For public interface changes proposals will need to be developed
and submitted to the AFS3 Standardization mailing list for review
and obtaining consensus.  The result should be an Internet-Draft
style document that can be used as an AFS3 standard for use by
implementers.

For the local and internal changes they need to be submitted for
review on the OpenAFS developers list prior to implementation.
Tools providing for forward and backward migration should accompany
on-disk format changes.

Jeffrey Altman


Mauricio Villarroel wrote:
> Thanks Jeffrey for the quick response.
> 
> Is someone currently working on this?, I would love give a hand with
> this if there is a list somewhere of changes and tasks needed.
> 
> Mauro
> 
> On Mon, Aug 31, 2009 at 7:18 PM, Jeffrey Altman
> <jaltman@secure-endpoints.com <mailto:jaltman@secure-endpoints.com>> wrote:
> 
>     Mauricio Villarroel wrote:
> 
>     > What is the limit for a volume?. I read online that one possible
>     source
>     > of the limitation comes from some data structure that are using 32bits
>     > "ints" and changing them would mean changing the AFS communication
>     > protocol?, if this is the case, is there a plan to increase it?
> 
>     The volume limit is 2^31 (max signed int).
> 
>     Raising this limit requires introducing a new set of RPCs, modifying the
>     on-disk format, creating disk format conversion tools, etc.   Yes: we
>     want to do it.  No: there is no scheduled timeline for doing so.
>     However, we would prefer it to be sooner rather than later.
> 
>     Jeffrey Altman
> 
> 
> 
>