All of lore.kernel.org
 help / color / mirror / Atom feed
From: DENIEL Philippe <philippe.deniel@cea.fr>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: READDIRPLUS3 and NFS3ERR_BAD_COOKIE
Date: Thu, 22 Mar 2012 13:45:39 +0100	[thread overview]
Message-ID: <4F6B1EF3.2000200@cea.fr> (raw)

Hi,

what is the client's behavior if NFS3ERR_BAD_COOKIE is replied by 
READDIRPLUS3 ?
I have this error when running bonnie++ on top of my (non knfsd) server. 
At this step bonnie++ readdirs all dentries and erase them. One of the 
readdir calls ends with NFS3ERR_BAD_COOKIE and immediatly after, the 
client is calling RMDIR3, without having removed any of the found 
dentries. Of course RMDIR3 replies NFS3ERR_NOT_EMPTY, but I do not 
understand why REMOVE is not called. It looks like the clients behaves 
that the directory is empty after having received NFS3ERR_BAD_COOKIE 
(that just an hypothesis, I am not just this is what actually happens).
Do you have any idea ?

    Regards

       Philippe

             reply	other threads:[~2012-03-22 12:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 12:45 DENIEL Philippe [this message]
2012-03-22 17:07 ` READDIRPLUS3 and NFS3ERR_BAD_COOKIE Myklebust, Trond
2012-03-22 17:14   ` DENIEL Philippe
2012-03-22 17:16     ` Myklebust, Trond

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=4F6B1EF3.2000200@cea.fr \
    --to=philippe.deniel@cea.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.