From: Jan Psota <jasiu@belsznica.pl>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: refcount underflow in nfsd41_destroy_cb
Date: Sun, 22 Mar 2020 04:43:52 +0100 [thread overview]
Message-ID: <20200322044352.2ff1fbd8.jasiu@belsznica.pl> (raw)
In-Reply-To: <44C9D860-4F51-46B1-88A3-D10DDEF4BD8E@oracle.com>
Chuck Lever <chuck.lever@oracle.com> napisał(a):
> Jan, how are you reproducing this?
It looks like it's taking place on server on high NFS load and about
a day after boot! (as I noticed looking into last -x results, below)
Then system runs all right for a month (to be rebooted on new kernel
[not always] or something like this).
We have some NFS-rooted machines:
/systemd on / type nfs4 (rw,relatime,vers=4.2,rsize=4096,wsize=4096,namlen=255,hard,proto=tcp,
timeo=10,retrans=2,sec=sys,clientaddr=192.168.1.18,local_lock=none,addr=192.168.1.1)
Server has 10Gb Aquantia AQC107 card connected to Mikrotik CSS326
switch. Clients running distcc (aside from acting as workstations)
are connected on 1Gb ethernet. Server runs Gentoo Linux on OpenRC
(stations have Systemd) with recent gcc-9.3, binutils-2.34 and
glibc-2.30, has 32 GB RAM and AMD Phenom II X6 1090T CPU.
/var/tmp/portage, where compilation takes place, normally is on client
tmpfs, but when there is not enough space to compile huge program, I
switch it to server exported NFS
(/etc/exports opts: -rw,async,no_root_squash,no_subtree_check)
# "grep nfs.*destroy /var/log/messages" mixed with "last -x"
reboot system boot 5.5.1-gentoo Mon Feb 3 00:20 - 15:22 (25+15:01)
Feb 4 17:44:39 agro kernel: nfsd41_destroy_cb+0x2c/0x40 [nfsd]
rust compilation, kernel 5.5.1-gentoo
reboot system boot 5.5.6-gentoo Fri Feb 28 15:23 - 16:25 (14+01:02)
Feb 29 13:51:49 agro kernel: nfsd41_destroy_cb+0x2c/0x40 [nfsd]
rust compilation, kernel 5.5.6-gentoo
reboot system boot 5.5.9-gentoo Fri Mar 13 16:27 - 00:04 (4+07:36)
Mar 14 18:03:49 agro kernel: nfsd41_destroy_cb+0x2c/0x40 [nfsd]
libpciaccess compilation, kernel
reboot system boot 5.6.0-rc6 Wed Mar 18 00:06 - 20:39 (2+20:32)
Mar 19 11:08:07 agro kernel: nfsd41_destroy_cb+0x36/0x50 [nfsd]
linux-firmware merge
*
reboot system boot 5.6.0-rc6 Fri Mar 20 20:40 - 02:40 (05:59)
Mar 20 21:43:34 agro kernel: nfsd41_destroy_cb+0x36/0x50 [nfsd]
zstd compilation
*
reboot system boot 5.6.0-rc6 Sat Mar 21 02:42 still running
Mar 21 17:34:43 agro kernel: nfsd41_destroy_cb+0x36/0x50 [nfsd]
nodejs compilation
* - I noticed kernel fault looking for a reason, why WireGuard refused
to connect with _some_ remote peers so I rebooted the server and it helped.
next prev parent reply other threads:[~2020-03-22 3:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 2:51 refcount underflow in nfsd41_destroy_cb Jason A. Donenfeld
2020-03-21 14:41 ` Jan Psota
2020-03-21 17:25 ` Jan Psota
2020-05-10 23:23 ` Jan Psota
2020-05-15 22:01 ` J. Bruce Fields
2020-03-21 19:50 ` Chuck Lever
2020-03-22 3:43 ` Jan Psota [this message]
2020-03-23 14:13 ` Chuck Lever
2020-03-23 15:09 ` Jan Psota
2020-03-24 13:50 ` Chuck Lever
2020-03-31 17:59 ` Chuck Lever
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=20200322044352.2ff1fbd8.jasiu@belsznica.pl \
--to=jasiu@belsznica.pl \
--cc=Jason@zx2c4.com \
--cc=chuck.lever@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.