On Thu, Sep 3, 2015 at 3:26 PM, Olga Kornievskaia <aglo@xxxxxxxxx> wrote: > > When file is opened with O_DIRECT, sending asynchronous CLOSE creates > a race condition between CLOSE and DELEGRETURN followed REMOVE. Next > operations are sent before the reply for CLOSE comes back which is > according to the spec is not allowed (section 10.4.4). Server can get > a REMOVE before the CLOSE and it causes EACCESS error to be returned > because server thinks there is open state left. BTW: What is generating an EACCES here? AFAIK, if the REMOVE returns NFS4ERR_FILE_OPEN, then the client translates that as EBUSY (after first retrying the REMOVE a couple of times). -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
