From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 202441] Possibly vfs cache related replicable xfs regression since 4.19.0 on sata hdd:s
Date: Tue, 23 Nov 2021 15:43:58 +0000 [thread overview]
Message-ID: <bug-202441-201763-2GZTXzAYPG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202441-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202441
Sami Farin (hvtaifwkbgefbaei@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hvtaifwkbgefbaei@gmail.com
--- Comment #28 from Sami Farin (hvtaifwkbgefbaei@gmail.com) ---
[....] When vfs_cache_pressure=0, the kernel will never
reclaim dentries and inodes due to memory pressure and this
can easily lead to out-of-memory conditions. [....]
I wish that was true. I have it set to 0, and I have 32 GiB RAM of which 23 GiB
free when doing the test using XFS filesystem:
$ du -sh
$ sleep 60
# (dentries forgotten, the next du takes a minute to run (SATA rust platter
disk))
$ du -sh
kernel 5.10.80. No swap.
MemTotal: 32759756 kB
MemFree: 23807992 kB
MemAvailable: 23774316 kB
Buffers: 24 kB
Cached: 765240 kB
SwapCached: 0 kB
Active: 290420 kB
Inactive: 3859348 kB
Active(anon): 168968 kB
Inactive(anon): 3720380 kB
Active(file): 121452 kB
Inactive(file): 138968 kB
Unevictable: 18304 kB
Mlocked: 18304 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 56 kB
Writeback: 0 kB
AnonPages: 3391352 kB
Mapped: 310564 kB
Shmem: 496832 kB
KReclaimable: 196444 kB
Slab: 2197440 kB
SReclaimable: 196444 kB
SUnreclaim: 2000996 kB
KernelStack: 25728 kB
PageTables: 67676 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 15855588 kB
Committed_AS: 17433636 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 392660 kB
VmallocChunk: 0 kB
Percpu: 43264 kB
HardwareCorrupted: 0 kB
AnonHugePages: 1015808 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
HugePages_Total: 512
HugePages_Free: 512
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
Hugetlb: 1048576 kB
DirectMap4k: 27877496 kB
DirectMap2M: 5607424 kB
DirectMap1G: 1048576 kB
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2021-11-23 15:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 20:41 [Bug 202441] New: Possibly vfs cache related replicable xfs regression since 4.19.0 on sata hdd:s bugzilla-daemon
2019-01-28 22:00 ` Dave Chinner
2019-01-28 22:00 ` [Bug 202441] " bugzilla-daemon
2019-01-28 23:26 ` bugzilla-daemon
2019-01-29 0:29 ` Dave Chinner
2019-01-29 0:29 ` bugzilla-daemon
2019-01-29 0:43 ` bugzilla-daemon
2019-01-29 1:23 ` Dave Chinner
2019-01-29 0:47 ` bugzilla-daemon
2019-01-29 1:23 ` bugzilla-daemon
2019-01-29 3:36 ` bugzilla-daemon
2019-01-29 9:09 ` bugzilla-daemon
2019-01-29 9:11 ` bugzilla-daemon
2019-01-29 9:27 ` bugzilla-daemon
2019-01-29 9:29 ` bugzilla-daemon
2019-01-29 17:55 ` bugzilla-daemon
2019-01-29 21:41 ` Dave Chinner
2019-01-29 21:19 ` bugzilla-daemon
2019-01-29 21:44 ` Dave Chinner
2019-01-29 21:41 ` bugzilla-daemon
2019-01-29 21:53 ` Dave Chinner
2019-01-29 21:44 ` bugzilla-daemon
2019-01-29 21:53 ` bugzilla-daemon
2019-01-29 22:07 ` bugzilla-daemon
2019-01-29 22:19 ` bugzilla-daemon
2019-01-29 22:23 ` bugzilla-daemon
2019-01-29 22:39 ` bugzilla-daemon
2019-01-29 23:03 ` bugzilla-daemon
2019-01-29 23:28 ` Dave Chinner
2019-01-29 23:28 ` bugzilla-daemon
2019-01-29 23:35 ` bugzilla-daemon
2019-01-30 10:50 ` bugzilla-daemon
2019-01-30 12:00 ` bugzilla-daemon
2019-02-01 21:59 ` bugzilla-daemon
2019-02-03 8:12 ` bugzilla-daemon
2021-11-23 15:43 ` bugzilla-daemon [this message]
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=bug-202441-201763-2GZTXzAYPG@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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.