Date: Wed, 13 Mar 2019 14:13:25 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 236510] ZFS ARC usage causes mlock(2) to fail with EAGAIN Message-ID: <bug-236510-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236510 Bug ID: 236510 Summary: ZFS ARC usage causes mlock(2) to fail with EAGAIN Product: Base System Version: 11.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: martin@lispworks.com Attachment #202843 text/plain mime type: Created attachment 202843 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D202843&action= =3Dedit mlocktest.c I am running 11.2-p5. With the default settings of vm.max_wired and vfs.zfs.arc_max, compile and = run the attached mlocktest.c on a ZFS filer where ARC is using more than 1/3 of RAM. It is very likely to fail with mlocktest: mlock: Resource temporarily unavailable Other examples are gpg and pinentry-tty which will complain about using insecure memory. The problem is that mlock(2) fails when vm.stats.vm.v_wire_count > vm.max_wired. This is fine when there is little else using wired memory, b= ut ZFS ARC seems to be a large user of it. Of course vfs.zfs.arc_max could be decreased or vm.max_wired could be increased, but this doesn't seem sensibl= e on a ZFS file server that only needs a small amount of mlock'ed memory. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236510-227>