[Federated-fs] fs_root in federated namespace

[Raj, Theresa]

I have a question about the fs_root value provided by fileservers as
part of the FS_LOCATIONS attribute. This also kind of ties into the root
namespace discussion that's recently come up on the list.
 
In the federated namespace, a fileserver's fileset is hanging off
someplace within the namespace. And it is not incumbent upon the
fileserver to know about where this fileset is hanging in the namespace,
i.e., the fileserver need not know the pathname from the root of the
namespace that leads to the junction that has the FSL pointing to this
fileserver and this fileset. 
 
So now if there is a junction embedded in its fileset, the fileserver is
required to provide the FS_LOCATIONS attribute for that junction. For
the server, rootpath details of that junction the NSDB has that
information and the fileserver will obtain those from the NSDB. But for
the fs_root part of this attribute, how can the fileserver construct the
full pathname to that junction. The fileserver can figure out the
portion of the pathname that is within its fileset but not the
antecedent portion of the pathname.
 
I think that the fileserver needs some help to figure the fs_root value.
How that can be achieved in another discussion.
 
Thanks,
Theresa
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.sdsc.edu/pipermail/federated-fs/attachments/20080616/c34c5a38/attachment.html