[AFS3-std] Snapshot Identifiers

[Hartmut Reuter]

With these giant numbers of snapshots I see some other problems:

If there should coexist multiple snapshots in the same partition
belonging to the same volume group the present design of the linktable
of the NAMEI-fileserver will break because it allows only a limited
number of versions (5) and a limited value for the link count (7) per
version of a vnode number's data.

Also if the volume id should become 64 bit certainly the NAMEI mapping
algorithm of volume ids to directory trees would have to change.
This change would not only affect the fileserver, volserver and
salvager, but also rxosd.

Hartmut

Matt W. Benjamin wrote:
> So the AFS protocol should provide access to the best available
> snapshot available relative to a point in time.  Does that mandate
> that snapshot generations are best regarded in the protocol as a
> timestamp per se?  I don't believe so.  Doing so appears to conflate
> a temporal search criteria with an ordinal (or opaque identifier).
> It misbehaves near the maximum resolution, and seems to carry the
> assumption that all implementations will be producing effectively
> continuous snapshots.
> 
> _______________________________________________ AFS3-standardization
> mailing list AFS3-standardization@openafs.org 
> http://michigan-openafs-lists.central.org/mailman/listinfo/afs3-standardization
> 
> 
> _______________________________________________ AFS3-standardization
> mailing list AFS3-standardization@openafs.org 
> http://michigan-openafs-lists.central.org/mailman/listinfo/afs3-standardization
> 
-- 
-----------------------------------------------------------------
Hartmut Reuter                  e-mail 		reuter@rzg.mpg.de
			   	phone 		 +49-89-3299-1328
			   	fax   		 +49-89-3299-1301
RZG (Rechenzentrum Garching)   	web    http://www.rzg.mpg.de/~hwr
Computing Center of the Max-Planck-Gesellschaft (MPG) and the
Institut fuer Plasmaphysik (IPP)
-----------------------------------------------------------------