Linux-NFS Archive on lore.kernel.org
 help / color / Atom feed
From: Gefei Li <gefeili.2013@gmail.com>
To: linux-nfs@vger.kernel.org
Cc: "J. Bruce Fields" <bfields@fieldses.org>
Subject: Did NFS client hang all OPEN request after SEQ4_STATUS_EXPIRED_SOME_STATE_REVOKED flag is set?
Date: Sat, 28 Sep 2019 00:56:34 +0800
Message-ID: <CANidX5SdiM3fZ+A1N_Z4iNhMU8KSvSHqwRXciyX32ZqDzLH32w@mail.gmail.com> (raw)

Hi Kernel NFS devs,

From RFC 5661, I know that the flag
SEQ4_STATUS_EXPIRED_SOME_STATE_REVOKED may be a "time-consuming" flag
for client, when received this flag, client needs to check all
existing lock/state.

   SEQ4_STATUS_EXPIRED_SOME_STATE_REVOKED
      When set, indicates that some subset of the client's locks have
      been revoked due to expiration of the lease period followed by
      another client's conflicting LOCK operation.  This status bit
      remains set on all SEQUENCE replies until the loss of all such
      locks has been acknowledged by use of FREE_STATEID.

My question is: when client received this flag, did it hang all
incoming "open" syscall on NFS files before the lock/state check
finished?

The problem I met is that my linux VM(with kernel 5.2.11) gives me a
really slow response(sometimes after an hour) after my NFS
traffic(which is heavy) runs for a while, I want to know the root
cause for this slow syscall, and from some packet trace I can get this
flag in some response of SEQUENCE response.

Appreciate your help and thanks in advance.

Thanks,
Gefei

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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=CANidX5SdiM3fZ+A1N_Z4iNhMU8KSvSHqwRXciyX32ZqDzLH32w@mail.gmail.com \
    --to=gefeili.2013@gmail.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

Linux-NFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-nfs/0 linux-nfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nfs linux-nfs/ https://lore.kernel.org/linux-nfs \
		linux-nfs@vger.kernel.org
	public-inbox-index linux-nfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-nfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git