I'm looking for feedback from anyone who has experience or a naming scheme for volumes within large projects. We have several projects in our cell that are over 100 MB in size. Our site has tried to follow the 100MB/Volume rule, thus these larger projects constitute several AFS volumes. The current scheme is to have the volume name set to: "proj.<project_name>", and subsequent volumes be named after subdirectories under the parent project: "proj.<project_name>.<subdir>..." This works, but we often hit the 22 char limit for names, and the association between mount points and volumes (not sure how important this really is) can be altered when the user decides to remove the mount point and mount the volume under a newly named mount point. I'm considering two possibilities. First, allowing these "larger" projects to have volume quotas greater than 100MB, but then where do you draw the line? Secondly, user accounts who have reached the 100MB limit are assigned volumes using the following scheme: "user.<user_name>.spare1" where the "spare1" volume gets mounted wherever they decide. This would be another possibility, but I feel users do need some tools ( other than fs and vos) to determine the association between volumes and their subdirs. Finally, what if the entire project gets munched? Then the admin needs to know how to restore volumes and remount them to obtain original directory structure... Any thoughts/ideas/experiences would be appreciated. Troy Thompson ([EMAIL PROTECTED]) Battelle NW Labs Richland WA 99352
