Bug 231794 - zfs: Panic due to ARC related KVA memory exhaustion: in pmap_growkernel() > vm_map_insert
Summary: zfs: Panic due to ARC related KVA memory exhaustion: in pmap_growkernel() > v...
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 11.2-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: Mark Linimon
URL:
Keywords: crash, needs-qa
Depends on:
Blocks:
 
Reported: 2018-09-29 00:30 UTC by Dave Robison
Modified: 2024-10-04 11:38 UTC (History)
6 users (show)

See Also:
koobs: mfc-stable13?
koobs: mfc-stable12?


Attachments
Photo of backtrace (710.11 KB, image/png)
2018-09-29 00:30 UTC, Dave Robison
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Robison 2018-09-29 00:30:16 UTC
Created attachment 197582 [details]
Photo of backtrace

We are evaluating two servers based on the HP DL360 G10 (16 gigs RAM) and HP DL380 G10 (32 gigs RAM) motherboards. We can routinely panic these machines by putting them under load while running ZFS. Running six instances of bonnie++ and six instances of memtester (testing 2g) is enough to panic the DL360 in around 15 minutes and the DL380 in 10-13 hours.

Reducing ARC dramatically using vfs.zfs.arc_min and vfs.zfs.arc_max seems to mitigate this problem, at least after a day of testing under 12.0-A7. We are testing now on 11.2-RELEASE which we will use in production.

Daiichi from Japan was here to help diagnose this problem, and has been in contact with core team members who requested this bugzilla submission.

More panic photos available on request.
Comment 1 rainer 2018-10-04 06:59:54 UTC
See also:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296

There's something seriously wrong with the default settings.
Comment 2 Andriy Gapon freebsd_committer freebsd_triage 2018-10-04 14:39:37 UTC
(In reply to Dave Robison from comment #0)
I just want to note that the problem here is not with exhausting the physical memory, but rather with exhausting the kernel virtual address space (KVA).
There could be many reasons for that such as incorrect tuning, bugs, KVA fragmentation, etc.
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2022-11-01 23:53:09 UTC
^Triage: Report is for EoL 11.2 (12.0-ALPHA7). Needs reproduction against currently supported versions.
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2024-10-04 11:38:04 UTC
^Triage: close as OBE.  I'm sorry we never properly investigated this PR.