From: Ulrich Gemkow <ulrich.gemkow@ikr.uni-stuttgart.de>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: NFS Server prevents access to files on different scenarios (lock problem?)
Date: Thu, 17 Nov 2016 21:32:47 +0100 [thread overview]
Message-ID: <201611172132.47523.ulrich.gemkow@ikr.uni-stuttgart.de> (raw)
Hello,
we use Linux NFS clients with a Linux NFS server in an configuration
where NFS mounts are done on client boot _and_ on user login in a
session; umounts are done on users logout from the session.
We see occasionally several different problems which all may have
the same root cause:
- When a client accesses a file which was accessed before
from the same client in a previous session the server
prevents access to the file until a timeout happens.
The timeout has a duration of about 1-3 minutes.
In this case the "blocked" file can not even be deleted
on the server.
--> What causes this timeout? I found nothing in the
server code which has such a timeout How can I debug what
the server is waiting for or why he is blocking access
to the file?
- Sometimes client processes hang in the middle of a session
on some file. After a timeout the file is accessible again.
The timeout can take 1 upto several minutes. The file is
also blocked on the server, it cannot be accessed.
I think all theses problemes are caused by something like
dangling locks or another invalid state on the server.
The clients show no network error like dropped packets
or something like this.
--> How can I debug such hangs?
We use Linux NFS server and client from vanilla kernel 4.4.31
with sec=sys.
Can anyone help? Does "a bell ring"?
Thank you and best regards
-Ulrich
--
| Ulrich Gemkow
| University of Stuttgart
| Institute of Communication Networks and Computer Engineering (IKR)
next reply other threads:[~2016-11-17 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 20:32 Ulrich Gemkow [this message]
2016-11-17 21:04 ` NFS Server prevents access to files on different scenarios (lock problem?) J. Bruce Fields
2016-11-17 21:34 ` Ulrich Gemkow
2016-11-18 16:58 ` J. Bruce Fields
2016-11-18 18:55 ` Ulrich Gemkow
2016-11-18 20:47 ` J. Bruce Fields
2016-11-20 11:33 ` Ulrich Gemkow
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=201611172132.47523.ulrich.gemkow@ikr.uni-stuttgart.de \
--to=ulrich.gemkow@ikr.uni-stuttgart.de \
--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).