Giovanni Bracco wrote: > In our AFS space the user home consists on an AFS volume (located on a file > server in the geographical site where the most relevant computational > resources for the user are located) under which other user related AFS > volumes in other geographical sites are also mounted. > > When the user explores the content of the backup version of his main home > volume the mounts points of his volumes on other sites lead him NOT to their > backup version but to the related RW volumes and this is very confusing for > the user. > > This would be avoided if the navigation criteria for backup volumes were > almost analogous to the criteria for the navigation in RO volumes, that is > AFS should automatically provide the access to the BK version if the mount > point is itself in a BK volume and a BK volume exists. > > Would that be possible? > > Are there other solutions for the problem? > Hi,
Have you tried using the -backuptree option for starting the "afsd" process on the client? See the afsd man page or http://www.openafs.org/cgi-bin/cvsweb.cgi/openafs/doc/man-pages/pod8/afsd.pod?rev=1.10&content-type=text/x-cvsweb-markup That sounds like what you want. Sincerely, Jason _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info