From: Andrei Warkentin <awarkentin@vmware.com>
To: linux-nfs@vger.kernel.org
Cc: Ed Goggin <egoggin@vmware.com>
Subject: Re: stale or not stale
Date: Thu, 2 Aug 2012 19:29:14 -0700 (PDT) [thread overview]
Message-ID: <1592211005.4733808.1343960954717.JavaMail.root@vmware.com> (raw)
In-Reply-To: <1781697815.4540720.1343959078882.JavaMail.root@vmware.com>
----- Original Message -----
> From: "Ed Goggin" <egoggin@vmware.com>
> To: linux-nfs@vger.kernel.org
> 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
next prev parent reply other threads:[~2012-08-03 2:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 1:57 stale or not stale Ed Goggin
2012-08-03 2:29 ` Andrei Warkentin [this message]
2012-08-03 10:52 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1592211005.4733808.1343960954717.JavaMail.root@vmware.com \
--to=awarkentin@vmware.com \
--cc=egoggin@vmware.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).