Re: [nfsv4] [FedFS] Meeting Minutes, 9/30/2010

[James Lentini <[e-mail]>]

On Thu, 30 Sep 2010, Chuck Lever wrote:

> 
> On Sep 30, 2010, at 3:51 PM, James Lentini wrote:
> 
> > 
> > FedFS Meeting Minutes, 9/30/2010
> > --------------------------------
<snip>
> > - What should be the error if an FSL object is missing information? There 
> >   is an existing error code, FEDFS_ERR_NSDB_RESPONSE, for malformed 
> >   responses. We'll expand on the description of this error to note some of 
> >   situations (like this one) in which it should be used.
> 
> ...and clarify the differences between FEDFS_ERR_NSDB_RESPONSE, 
> FEDFS_ERR_NSDB_FAULT, and FEDFS_ERR_NSDB_LDAP{_VAL}.

Not a problem.

> 
> In addition, the NSDB_RESPONSE error code can be returned by the 
> ADMIN protocol's FEDFS_LOOKUP_JUNCTION procedure.  

Correct, this is a valid error value for FEDFS_LOOKUP_JUNCTION.

> The specific question I had is how an NFS fileserver should reply to 
> GETATTR(fs_locations) if the NSDB returns obviously broken FSL 
> information.

Sorry for unintentionally leaving this out of the minutes.
 
> Some convention for the NFS server's reply in this case should be 
> agreed upon outside of the ongoing FedFS discussion.

I think another way to phrase this question is: How does an NFS server 
indicate that a file system has moved to an unknown location? One 
obvious possibility is to return a zero element locations array in the 
fs_locations structure.