Jay,
unfortunately there is no easy way to figure out which
mountpoint corresponds to which volume from the volume's
view point ...
One possibility is to parse down the whole (!) AFS tree on
your site and to check each directory if it is a mountpoint.
Then, collect this information and check it against the
list of available volumes.
We at ZIB have written a program which uses the
corresponding function calls. Others have written
scripts which combine the fs calls. However, we have
investigated problems when putting AFS under heavy load
which are caused by these recursive tree traversals.
Sometimes our machines have drift into boot land ...
If you have a volume which you think is not accessible
due to a missing mount point, just mount the volume and
investigate its content. You should be able to figure
out where the mount point should be.
Anyway, if someone have a solution to this, I would be
more than happy to hear about it.
Question: Does the described behaviour of AFS under heavy
load still occurs with AFS 3.4x?
Regards
Peter Mueller
