----- Original Message ----- > From: "Ed Goggin" <egoggin@xxxxxxxxxx> > To: linux-nfs@xxxxxxxxxxxxxxx > Sent: Thursday, August 2, 2012 9:57:58 PM > Subject: stale or not stale > > > It seems that nfsd can return reply attributes with a link count of > zero but without an NFS3ERR_STALE status. We've seen this actually > happen for a write request to a file with a single link that is > concurrently being removed without NLM lock protection. What is the > proper behavior here? I think it would be worthwhile to add here that the the remove was not concurrent with the write, and at the time of the NFS write a new file with the same name existed, yet fh decoding picked up the old inode instead of reporting -ESTALE. FS was ext4. In fact seen two things happen - n_link = 0 and n_link = 1, and in both cases we knew the file was unlink()ed and re-creat()ed. A -- 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
