"Neulinger, Nathan" <[EMAIL PROTECTED]> writes:
> Something as simple as having an alternative namei that would look the
> same down below, but would have the top level directory be the RW volume
> id corresponding to whatever data is being stored.
Um, the top-level directory (well, two top-level dirs) already is
(are) the volume id. It's just encoded in base64, and split into
two sets of bits. But it's still the volumeID. E.g.
./+/++++U/+/+/0++++6
./1/1+++U/special/zzzzPA++++0
These are in two different volumes.
> This would allow the top level dirs and volume header to be backed up
> and restored as regular files. Granted you would not have the true
> snapshot like you can get with vos, but even that is subject to timing
> as far as high level file access goes.
Current namei already gives you that, actually.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
