Re: [nfsv4] RENAME and NFS4ERR_ISDIR

cburnett@us.ibm.com

Subject: Re: [nfsv4] RENAME and NFS4ERR_ISDIR
Message-ID: <OF4CC0CD62.80DB308D-ON87256E30.0063664A-86256E30.006364C4@us.ibm.com>
From: Carl Burnett <cburnett@us.ibm.com>
Date: Wed, 4 Feb 2004 12:07:58 -0600

Can this get done ASAP. I would like to change our server with the comfort 
that its in spec. I would also like to know what the other errors you 
refer to below are.

Thanks,
Carl

Carl Burnett
AIX Kernel Architecture - Network File System
(512) 838-8498, TL 678-8498
(please reply to cburnett@us.ibm.com)

Spencer Shepler <spencer.shepler@sun.com>
Sent by: nfsv4-admin@ietf.org
02/04/2004 11:33 AM

        To:     "Noveck, Dave" <Dave.Noveck@netapp.com>
        cc:     <nfsv4@ietf.org>, Carl Burnett/Austin/IBM@IBMUS
        Subject:        Re: [nfsv4] RENAME and NFS4ERR_ISDIR

Note, we are able to submit RFC errata for this type of change.  We 
have one
or two other error code changes that have been mentioned in the past
that should be included in the errata as well.

Spencer

On Feb 4, 2004, at 10:57 AM, Noveck, Dave wrote:

>> What's the correct thing to do. I think NFS4ERR_ISDIR should be 
>> allowed
>> for RENAME.
>
> I agree but how (procedurally) do we make that happen?
>
> RFC 3530 is set in stone but is it sandstone, granite, or what?
>
> I assume we can address stuff like that in v4.1 (in addition to
> the bigger stuff like sessions and directory delegation) but how
> can we change v4.0, in the meantime?
>
> Making this change doesn't really cause an incompatibility.  Nobody,
> except a hypothetical test suite would be depending on NFS4ERR_ISDIR
> not being returned by RENAME.  Supposing that this clears the first
> hurdle, of the working group thinking this is a good thing to do,
> what other hurdles are there?
>
>
>
> -----Original Message-----
> From: Carl Burnett [mailto:cburnett@us.ibm.com]
> Sent: Wednesday, February 04, 2004 10:54 AM
> To: nfsv4@ietf.org
> Subject: [nfsv4] RENAME and NFS4ERR_ISDIR
>
>
> The RENAME operation does not list NFS4ERR_ISDIR as a valid error.
>
> POSIX states that if you try to rename a file to a directory (oldpath 
> is
> file, newpath is a dir), EISDIR should be returned. Without allowing
> NFS4ERR_ISDIR as a valid return, the POSIX behavior cannot be achieved
> with NFSv4.
>
> Currently, the spec seems to suggest that NFS4ERR_EXIST should be
> returned. -
>
>         "If they are not  compatible or if the target is a directory 
> but
> not empty, the server will return the error, NFS4ERR_EXIST."
>
> We noticed in testing with the Solaris beta download, that the server
> looks to be returning NFS4ERR_ISDIR in this case, which per the spec 
> would
> be non-compliant. But of course, it allows POSIX behavior.
>
> What's the correct thing to do. I think NFS4ERR_ISDIR should be allowed
> for RENAME.
>
> Thanks,
> Carl
>
>
> Carl Burnett
> AIX Kernel Architecture - Network File System
> (512) 838-8498, TL 678-8498
> (please reply to cburnett@us.ibm.com)
>
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www1.ietf.org/mailman/listinfo/nfsv4
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www1.ietf.org/mailman/listinfo/nfsv4
>

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4