From: William Dauchy <william@gandi.net>
To: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>
Subject: strange behavior with nfsv3 using linux v4.1
Date: Fri, 6 Nov 2015 23:57:15 +0100 [thread overview]
Message-ID: <20151106225715.GH12546@gandi.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2993 bytes --]
Hello,
I am seeing strange behaviors with a single nfsv3 mount on linux
v4.1.x. I first started to see two kworker in D state while I was not
doing anything. The server is an opensolaris nfs server.
If I try to get more info I am seeing getattr loop as follow:
echo 65535 > /proc/sys/sunrpc/nfs_debug
NFS call getattr
NFS reply getattr: 0
NFS: nfs_update_inode(0:15/22630 fh_crc=0x1df1ef00 ct=1 info=0x27e7f)
NFS: (0:15/22630) revalidation complete
NFS: nfs_lookup_revalidate(x86_64-linux-gnu/libc-2.19.so) is valid
NFS: permission(0:15/22630), mask=0x24, res=0
NFS: open file(x86_64-linux-gnu/libc-2.19.so)
NFS: dentry_delete(x86_64-linux-gnu/libc.so.6, 6808cc)
NFS: read(x86_64-linux-gnu/libc-2.19.so, 832@0)
NFS: mmap(x86_64-linux-gnu/libc-2.19.so)
NFS: mmap(x86_64-linux-gnu/libc-2.19.so)
NFS: flush(x86_64-linux-gnu/libc-2.19.so)
NFS: permission(0:15/4), mask=0x81, res=0
NFS: nfs_lookup_revalidate(/etc) is valid
NFS: permission(0:15/12), mask=0x81, res=0
NFS: nfs_lookup_revalidate(etc/ld.so.nohwcap) is valid
NFS: permission(0:15/4), mask=0x81, res=0
NFS: nfs_lookup_revalidate(/lib) is valid
NFS: permission(0:15/14), mask=0x81, res=0
NFS: nfs_lookup_revalidate(lib/x86_64-linux-gnu) is valid
NFS: permission(0:15/1178), mask=0x81, res=0
NFS: nfs_lookup_revalidate(x86_64-linux-gnu/libpthread.so.0) is valid
NFS: permission(0:15/1178), mask=0x1, res=0
NFS: revalidating (0:15/22644)
NFS call getattr
NFS reply getattr: 0
NFS: nfs_update_inode(0:15/22644 fh_crc=0x9a566cc1 ct=1 info=0x27e7f)
NFS: (0:15/22644) revalidation complete
NFS: nfs_lookup_revalidate(x86_64-linux-gnu/libpthread-2.19.so) is valid
NFS: permission(0:15/22644), mask=0x24, res=0
NFS: open file(x86_64-linux-gnu/libpthread-2.19.so)
NFS: dentry_delete(x86_64-linux-gnu/libpthread.so.0, 6808cc)
NFS: read(x86_64-linux-gnu/libpthread-2.19.so, 832@0)
NFS: mmap(x86_64-linux-gnu/libpthread-2.19.so)
NFS: mmap(x86_64-linux-gnu/libpthread-2.19.so)
NFS: flush(x86_64-linux-gnu/libpthread-2.19.so)
NFS: release(etc/ld.so.cache)
NFS: dentry_delete(etc/ld.so.cache, 4808cc)
NFS: permission(0:15/4), mask=0x81, res=0
NFS: nfs_lookup_revalidate(/root) is valid
NFS: permission(0:15/20), mask=0x81, res=0
NFS: nfs_lookup_revalidate(root/.config) is valid
NFS: permission(0:15/4), mask=0x81, res=0
NFS: nfs_lookup_revalidate(/etc) is valid
NFS: permission(0:15/12), mask=0x81, res=0
NFS: nfs_lookup_revalidate(etc/terminal-colors.d) is valid
NFS: permission(0:15/4), mask=0x81, res=0
NFS: nfs_lookup_revalidate(/dev) is valid
NFS: permission(0:15/4), mask=0x81, res=0
NFS: nfs_lookup_revalidate(/var) is valid
NFS: permission(0:15/27), mask=0x81, res=0
NFS: nfs_lookup_revalidate(var/lib) is valid
NFS: permission(0:15/19882), mask=0x81, res=0
NFS: revalidating (0:15/19990)
[...]
Do you have some hints in order to help debug this issue?
If I reboot using my older v3.14.x with same config, I don't have that
behavior.
Best regards,
--
William
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2015-11-06 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 22:57 William Dauchy [this message]
2015-11-07 8:41 ` strange behavior with nfsv3 using linux v4.1 William Dauchy
2015-11-11 21:28 ` William Dauchy
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=20151106225715.GH12546@gandi.net \
--to=william@gandi.net \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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