From: Chuck Lever III <chuck.lever@oracle.com>
To: Jan Schunk <scpcom@gmx.de>
Cc: Jeff Layton <jlayton@kernel.org>, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [External] : nfsd: memory leak when client does many file operations
Date: Mon, 25 Mar 2024 20:11:23 +0000 [thread overview]
Message-ID: <088D9CC3-C5B0-4646-A85D-B3B9ACE8C532@oracle.com> (raw)
In-Reply-To: <trinity-ad0037c0-1060-4541-a8ca-15f826a5b5a2-1711396545958@msvc-mesg-gmx024>
> On Mar 25, 2024, at 3:55 PM, Jan Schunk <scpcom@gmx.de> wrote:
>
> The VM is now running 20 hours with 512MB RAM, no desktop, without the "noatime" mount option and without the "async" export option.
>
> Currently there is no issue, but the memory usage is still contantly growing. It may just take longer before something happens.
>
> top - 00:49:49 up 3 min, 1 user, load average: 0,21, 0,19, 0,09
> Tasks: 111 total, 1 running, 110 sleeping, 0 stopped, 0 zombie
> %CPU(s): 0,2 us, 0,3 sy, 0,0 ni, 99,5 id, 0,0 wa, 0,0 hi, 0,0 si, 0,0 st
> MiB Spch: 467,0 total, 302,3 free, 89,3 used, 88,1 buff/cache
> MiB Swap: 975,0 total, 975,0 free, 0,0 used. 377,7 avail Spch
>
> top - 15:05:39 up 14:19, 1 user, load average: 1,87, 1,72, 1,65
> Tasks: 104 total, 1 running, 103 sleeping, 0 stopped, 0 zombie
> %CPU(s): 0,2 us, 4,9 sy, 0,0 ni, 53,3 id, 39,0 wa, 0,0 hi, 2,6 si, 0,0 st
> MiB Spch: 467,0 total, 21,2 free, 147,1 used, 310,9 buff/cache
> MiB Swap: 975,0 total, 952,9 free, 22,1 used. 319,9 avail Spch
>
> top - 20:48:16 up 20:01, 1 user, load average: 5,02, 2,72, 2,08
> Tasks: 104 total, 5 running, 99 sleeping, 0 stopped, 0 zombie
> %CPU(s): 0,2 us, 46,4 sy, 0,0 ni, 11,9 id, 2,3 wa, 0,0 hi, 39,2 si, 0,0 st
> MiB Spch: 467,0 total, 16,9 free, 190,8 used, 271,6 buff/cache
> MiB Swap: 975,0 total, 952,9 free, 22,1 used. 276,2 avail Spch
I don't see anything in your original memory dump that
might account for this. But I'm at a loss because I'm
a kernel developer, not a support guy -- I don't have
any tools or expertise that can troubleshoot a system
without rebuilding a kernel with instrumentation. My
first instinct is to tell you to bisect between v6.3
and v6.4, or at least enable kmemleak, but I'm guessing
you don't build your own kernels.
My only recourse at this point would be to try to
reproduce it myself, but unfortunately I've just
upgraded my whole lab to Fedora 39, and there's a grub
bug that prevents booting any custom-built kernel
on my hardware.
So I'm stuck until I can nail that down. Anyone else
care to help out?
--
Chuck Lever
next prev parent reply other threads:[~2024-03-25 20:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 19:57 Jan Schunk
2024-03-24 20:14 ` [External] : " Chuck Lever III
2024-03-24 20:48 ` Aw: " Jan Schunk
2024-03-24 21:10 ` Chuck Lever III
2024-03-24 21:39 ` Aw: " Jan Schunk
2024-03-24 22:13 ` Chuck Lever III
2024-03-24 22:54 ` Aw: " Jan Schunk
2024-03-25 19:55 ` Jan Schunk
2024-03-25 20:11 ` Chuck Lever III [this message]
2024-03-25 20:26 ` Jan Schunk
2024-03-25 20:36 ` Chuck Lever III
2024-03-26 16:50 ` Aw: " Jan Schunk
2024-03-28 22:03 ` Jan Schunk
2024-03-29 0:25 ` Chuck Lever III
2024-03-30 15:26 ` Aw: " Jan Schunk
2024-03-30 16:26 ` Chuck Lever
2024-04-01 14:08 ` Chuck Lever III
2024-04-01 17:35 ` Aw: " Jan Schunk
2024-04-01 17:51 ` Chuck Lever III
2024-03-26 11:15 ` Benjamin Coddington
2024-03-26 17:04 ` Aw: " Jan Schunk
2024-03-26 17:13 ` Benjamin Coddington
2024-03-26 17:15 ` Benjamin Coddington
2024-03-26 19:05 ` Aw: " Jan Schunk
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=088D9CC3-C5B0-4646-A85D-B3B9ACE8C532@oracle.com \
--to=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=scpcom@gmx.de \
--cc=tom@talpey.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
all inboxes | Powered by JetHome®