All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kazi Anwar <kazia@srf-ext.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs4err_delay
Date: Fri, 24 Sep 2021 12:54:30 -0500	[thread overview]
Message-ID: <CAGw7ksJGjG0PUZqr+U+ssq_6YHgJ4cga40MCdpm8b_rYn1a5OA@mail.gmail.com> (raw)
In-Reply-To: <20210924163948.GB13115@fieldses.org>

Yes, both clients and server are centos 7.6. And the NFS4ERR_DELAY is
a response to a REMOVE.
I will need to check on the locks the next time it happens. Can you
share what you are thinking?

thanks,
Kazi

On Fri, Sep 24, 2021 at 11:39 AM J. Bruce Fields <bfields@fieldses.org> wrote:
>
> On Wed, Sep 22, 2021 at 03:56:23PM -0500, Kazi Anwar wrote:
> > We are running nfs v 4.1 on centos 7.6.
> > We are seeing an NFS issue where when files/dirs are deleted from a
> > client they are occasionally stuck at unlinkat system call(according
> > to strace its stuck for 100.5 secs every time). Can anyone explain
> > this behavior?
> > Running tcp dump shows nfs4err_delay status sent from the server to
> > the stuck client.
>
> Client and server are both centos 7.6?
>
> Is the NFS4ERR_DELAY a reponse to a REMOVE?
>
> Does /proc/locks show a delegation held on the file the client's trying
> to remove?
>
> --b.

  reply	other threads:[~2021-09-24 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 20:56 nfs4err_delay Kazi Anwar
2021-09-24 16:39 ` nfs4err_delay J. Bruce Fields
2021-09-24 17:54   ` Kazi Anwar [this message]
2021-09-24 19:03     ` nfs4err_delay J. Bruce Fields
  -- strict thread matches above, loose matches on Subject: below --
2012-08-21  8:25 NFS4: ssh + unlink(~/.Xauthority) delays Sven Geggus
2012-08-21  9:19 ` NFS4ERR_DELAY (was: NFS4: ssh + unlink(~/.Xauthority) delays) Sven Geggus
2012-08-21 10:41   ` Jeff Layton
2012-08-21 12:52     ` NFS4ERR_DELAY Sven Geggus
2012-08-21 13:07       ` NFS4ERR_DELAY Jeff Layton
2012-08-21 17:47         ` NFS4ERR_DELAY J. Bruce Fields
2012-08-22  8:33           ` NFS4ERR_DELAY Sven Geggus

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=CAGw7ksJGjG0PUZqr+U+ssq_6YHgJ4cga40MCdpm8b_rYn1a5OA@mail.gmail.com \
    --to=kazia@srf-ext.com \
    --cc=bfields@fieldses.org \
    --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.