Re: [nfsv4] CB_COPY list of errors (WAS: server-side copyoffloadI-D)

[anshul <[e-mail]>]

> 
> I'm talking about the actual srouce-destination transfer protocol. What
> happens if say FTP (mid-way through the transfer) gets an error from the
> source? It could be any of the FTP specific errors as described in
> RFC765. How does the current protocol propose dealing with the actual
> copy protocol errors and how would it enlighten the client about the
> same? What sorta of abstract error codes (as defined by this spec) would
> the actual copy protocol errors need to be mapped to, so that clients
> get a meaningful errors back for an admin to make sense of?

The actual error would have to be mapped to a valid NFSv4.1 error code
or any new error code that would be defined in this Spec. For the
example you describe i.e. if say FTP (mid-way through the transfer) gets
an error, - let us say the destination is out of space(I do not know the
corresponding FTP error), then the NFS client could be returned
NFS4ERR_NOSPC. 

Regards,
Anshul

> 
> - Pranoop
> 
> > 
> > Regards,
> > Anshul
> > 
> > >