[nfsv4] what error to return when there is more than one possibility

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: Carl Burnett (cburnett@us.ibm.com)
Date: 05/07/03-08:49:11 AM Z


Message-ID: <OF217F3FA5.4B8191AB-ON87256D1F.004867DF@us.ibm.com>
From: Carl Burnett <cburnett@us.ibm.com>
Subject: [nfsv4] what error to return when there is more than one possibility
Date: Wed, 7 May 2003 08:49:11 -0500

I have a question about what error a server should return when there are 
multiple possibilities. For example lets take open:

A client sends an OPEN to open a file for write access and deny read
The file is already opened for read by another open owner
The file system is a read-only file system

Should NFS4ERR_ROFS or NFS4ERR_SHARE_DENIED be returned?

In the above example, assume the open_owner (and thus the clientid) data 
is valid. So in that case the client's lease should be renewed. I think 
this means a server must at least do a bit of state management processing 
even when other basic checks result in errors. Is that correct?

As a variation on the above case, if the seqid where bad, should 
NFS4ERR_ROFS or NFS4ERR_BAD_SEQID be returned?

The general question is, which class of errors takes precedence, state or 
non state errors? If this is covered in the RFC, please point me at the 
appropriate spot(s). I want to bookmark it.

As a related question, should an open with (access_read, deny_write) be 
allowed against a read-only file system?


Thanks,
Carl

Carl Burnett
AIX Kernel Architecture - Distributed File Systems
(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


New Message Reply About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-02:12:21 AM Z CST