Linux NFS development
 help / color / mirror / Atom feed
From: Brian De Wolf <bldewolf@cpp.edu>
To: linux-nfs@vger.kernel.org
Subject: 3.14.27 client hang on specific file
Date: Thu, 18 Dec 2014 19:24:21 -0800	[thread overview]
Message-ID: <20141218192421.03a66cac@cpp.edu> (raw)

Hello,

After updating our kernel from 3.4.x to 3.14.27 (along with nfs-utils
1.2.9), we've had a strange issue with our sec=krb5p NFSv4 mounts.
My initial light testing went fine, but sometimes, on any given host, a
specific file will no longer be accessible.  Any attempt to access it
causes the process to go into uninterruptible sleep.

Reproducing this on another host was fairly quick by dd'ing 30MB
from /dev/zero into a file repeatedly.  Eventually the dd hangs instead
of completing.  Once broken, the simplest test I could think of was
"stat testfile".  tcpdump shows no traffic when I run it.  Turning
rpcdebug all the way up produces:

	kernel: RPC:       looking up Generic cred
	kernel: NFS: permission(0:28/3), mask=0x1, res=0
	kernel: NFS: nfs_lookup_revalidate(/testfile) is valid

Around the time that it breaks, it also prints

	kernel: nfs: server servername not responding, still trying

several times, but I couldn't find a way to get it to print it again.
It doesn't look like it follows up with more timeouts or an "OK", so
that seems pretty odd.

Anyone have any ideas?  I'm happy to provide more debug info.


Thanks,
Brian

             reply	other threads:[~2014-12-19  3:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19  3:24 Brian De Wolf [this message]
2014-12-23 23:28 ` 3.14.27 client hang on specific file Brian De Wolf

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=20141218192421.03a66cac@cpp.edu \
    --to=bldewolf@cpp.edu \
    --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