linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Cc: Andy Adamson <william.adamson@netapp.com>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	Steve Dickson <steved@redhat.com>
Subject: Lost CLOSE with NFSv4.1 on RHEL7 ( and bejond?)
Date: Thu, 7 Jul 2016 12:49:39 +0200 (CEST)	[thread overview]
Message-ID: <1485779983.22627050.1467888579184.JavaMail.zimbra@desy.de> (raw)



Dear NFS folks,

we observe orphan open-states on our deployment with nfsv4.1.
Our setup - two client nodes, running RHEL-7.2 with kernel
3.10.0-327.22.2.el7.x86_64. Both nodes running ownCloud (like
a dropbox) which nfsv4.1 mounts to dCache storage. Some clients
connected to node1, others to node2.

Time-to-time we see some 'active' transfers on data our DS
which do nothing. There is a corresponding state on MDS.

I have traced one one such cases:

  - node1 uploads the file.
  - node2 reads the file couple of times, OPEN+LAYOUTGET+CLOSE
  - node2 sends OPEN+LAYOUTGET
  - there is no open file on node2 which points to it.
  - CLOSE never send to the server. 
  - node1 eventually removes the removes the file

We have many other cases where file is not removed, but this one I was
able to trace. The link to capture files:

https://desycloud.desy.de/index.php/s/YldowcRzTGJeLbN

We had ~ 10^6 transfers in last 2 days and 29 files in such state (~0.0029%).

Tigran.

             reply	other threads:[~2016-07-07 10:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 10:49 Mkrtchyan, Tigran [this message]
2016-07-12 17:16 ` Lost CLOSE with NFSv4.1 on RHEL7 ( and bejond?) Adamson, Andy
2016-07-13 16:49   ` Mkrtchyan, Tigran
2016-07-14 14:52     ` Olga Kornievskaia
2016-08-01 11:08       ` Mkrtchyan, Tigran
2016-08-01 21:22         ` Olga Kornievskaia
2016-08-04 15:04           ` Mkrtchyan, Tigran
2016-08-04 19:00             ` Olga Kornievskaia
2016-08-04 21:20               ` Olga Kornievskaia
2016-08-09 10:57                 ` Mkrtchyan, Tigran

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=1485779983.22627050.1467888579184.JavaMail.zimbra@desy.de \
    --to=tigran.mkrtchyan@desy.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.com \
    --cc=trond.myklebust@primarydata.com \
    --cc=william.adamson@netapp.com \
    /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).