< 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>..."
Troy,
We have also large volume. We had defined partition on two physical
volumes - and we reach the maximum filesystem size -
On this 2 GB partition I create 1 volume (quota 1.9 GB) with no backup
(I mean "backupsys") But I have a backup on tape which need an other
2 GB partition in case of restore ...
On the other hand , I have "sub volume" :
/afs/../proj/<proj_name> mount point of volume proj.<proj_name>
/afs/../oldfile/proj/<proj_name> mntpoint of vol proj.<proj_name>.backup
1: I want to know the volume name from the PATH and vice versa
2: If I create a mount point of a secondary volume in this volume
I will have the same mount point in the oldfile path (backup of my
first volume) So I don't do that |
3: I create a hidden directory (dot) .<proj_name> (in oldfile too)
/afs/../proj/.<proj_name>/subdir mount point of proj.<proj_name>.subdir
and ln -sf
/afs/../proj/<proj_name>/subdir is a symbolique link on ../.<proj_name/subdir
So idem in path oldfile
/afs/../oldfile/proj/<proj_name>/subdir link on --> ../.<proj_name>/subdid
fs lsm ./subdir ==> is a symbolique link leading to the mount point of
volume proj.<proj_name>.subdir.backup
Vero.
