From: James Harvey <jamespharvey20@gmail.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Cc: bcodding@redhat.com
Subject: Re: 5.3.0 Regression: rpc.nfsd v4 uninterruptible sleep for 5+ minutes w/o rpc-statd/etc
Date: Thu, 19 Sep 2019 09:17:03 -0400 [thread overview]
Message-ID: <CA+X5Wn6Yj6752BMxpXB-wa92QQD7xv3uOp=rzJn5qP-_RxL41g@mail.gmail.com> (raw)
In-Reply-To: <CA+X5Wn60sGi+za48Lj-y1fcHHw7kdzEUsw8nj+Xc0U90mONz5w@mail.gmail.com>
On Thu, Sep 19, 2019 at 9:00 AM James Harvey <jamespharvey20@gmail.com> wrote:
>
> For a really long time (years?) if you forced NFS v4 only, you could
> mask a lot of unnecessary services.
>
> In /etc/nfs.conf, in "[nfsd] I've been able to set "vers3=n", and then
> mask the following services:
> * gssproxy
> * nfs-blkmap
> * rpc-statd
> * rpcbind (service & socket)
>
> Upgrading from 5.2.14 to 5.3.0, nfs-server.service (rpc.nfsd) has
> exactly a 5 minute delay, and sometimes longer.
>
> ...
P.S. During a few of the earlier boots where I was seeing strace show
the delay was reading "/proc/fs/nfsd/versions", I do have this in
journalctl, when I tried in another term cat'ing it during the
rpc.nfsd delay: (it repeats a few times during the 5 minute delay)
INFO: task cat:3400 blocked for more than 122 seconds.
Not tainted 5.3.0-arch1-1-ARCH #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
cat D 0 3400 3029 0x00000080
Call Trace:
? __schedule+0x27f/0x6d0
schedule+0x43/0xd0
schedule_preempt_disabled+0x14/0x20
__mutex_lock.isra.0+0x27d/0x530
write_versions+0x38/0x3c0 [nfsd]
? _copy_from_user+0x37/0x60
? write_ports+0x320/0x320 [nfsd]
nfsctl_transaction_write+0x45/0x70 [nfsd]
nfsctl_transaction_read+0x3b/0x60 [nfsd]
vfs_read+0x9d/0x150
ksys_read+0x67/0xe0
do_syscall_64+0x5f/0x1c0
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f47286fa155
Code: Bad RIP value.
RSP: 002b:00007ffcd2a74438 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007f47286fa155
RDX: 0000000000020000 RSI: 00007f47282ba000 RDI: 0000000000000003
RBP: 00007f47282ba000 R08: 00007f47282b9010 R09: 0000000000000000
R10: 0000000000000022 R11: 0000000000000246 R12: 00007f47282ba000
R13: 0000000000000003 R14: 0000000000000fff R15: 0000000000020000
svc: failed to register lockdv1 RPC service (errno 110).
lockd_up: makesock failed, error=-110
next prev parent reply other threads:[~2019-09-19 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 13:00 5.3.0 Regression: rpc.nfsd v4 uninterruptible sleep for 5+ minutes w/o rpc-statd/etc James Harvey
2019-09-19 13:17 ` James Harvey [this message]
2019-09-26 19:51 ` J. Bruce Fields
2019-10-01 18:21 ` Benjamin Coddington
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='CA+X5Wn6Yj6752BMxpXB-wa92QQD7xv3uOp=rzJn5qP-_RxL41g@mail.gmail.com' \
--to=jamespharvey20@gmail.com \
--cc=bcodding@redhat.com \
--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).