Date: Mon, 24 Sep 2018 17:44:14 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 231457] Out of swap space on ZFS Message-ID: <bug-231457-227-S1sTOxDyQp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231457-227@https.bugs.freebsd.org/bugzilla/> References: <bug-231457-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231457 Mike <mikeowens@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikeowens@gmail.com --- Comment #1 from Mike <mikeowens@gmail.com> --- Experiencing same issue. uname -a FreeBSD sword 11.2-RELEASE-p3 FreeBSD 11.2-RELEASE-p3 #0: Thu Sep 6 07:14:= 16 UTC 2018 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERI= C=20 amd64 swapinfo -h Device 1K-blocks Used Avail Capacity /dev/da0p2 12582912 4.2M 12G 0% /dev/da1p2 12582912 4.1M 12G 0% Total 25165824 8.3M 24G 0% sysctl hw | egrep 'hw.(phys|user|real)' hw.physmem: 34297905152 hw.usermem: 1263333376 hw.realmem: 34359738368 tail /var/log/messages Sep 24 12:30:29 sword kernel: pid 12993 (getty), uid 0, was killed: out of = swap space Sep 24 12:30:43 sword kernel: pid 12994 (getty), uid 0, was killed: out of = swap space Sep 24 12:30:58 sword kernel: pid 12995 (getty), uid 0, was killed: out of = swap space Sep 24 12:31:14 sword kernel: pid 12996 (getty), uid 0, was killed: out of = swap space Sep 24 12:31:28 sword kernel: pid 12997 (getty), uid 0, was killed: out of = swap space Sep 24 12:31:42 sword kernel: pid 12998 (getty), uid 0, was killed: out of = swap space Sep 24 12:31:57 sword kernel: pid 12999 (getty), uid 0, was killed: out of = swap space Sep 24 12:32:12 sword kernel: pid 13000 (getty), uid 0, was killed: out of = swap space Sep 24 12:32:27 sword kernel: pid 13001 (getty), uid 0, was killed: out of = swap space Sep 24 12:32:42 sword kernel: pid 13002 (getty), uid 0, was killed: out of = swap spac cat /boot/loader.conf accf_data_load=3D"YES" accf_http_load=3D"YES" autoboot_delay=3D3 cc_htcp_load=3D"YES" hw.igb.rx_abs_int_delay=3D1024 hw.igb.rx_int_delay=3D512 hw.igb.rxd=3D4096 hw.igb.tx_abs_int_delay=3D1024 hw.igb.tx_int_delay=3D512 hw.igb.txd=3D4096 hw.intr_storm_threshold=3D9000 if_bridge_load=3D"YES" if_tap_load=3D"YES" kern.geom.label.disk_ident.enable=3D"0" kern.geom.label.gptid.enable=3D"0" kern.ipc.nmbclusters=3D262144 kern.ipc.nmbjumbo16=3D32768 kern.ipc.nmbjumbo9=3D65536 kern.ipc.nmbjumbop=3D262144 kern.ipc.semaem=3D32767 kern.ipc.semmni=3D32767 kern.ipc.semmns=3D8192 kern.ipc.semmnu=3D4096 kern.ipc.semmsl=3D120 kern.ipc.semopm=3D200 kern.ipc.semume=3D80 kern.ipc.semusz=3D184 kern.ipc.semvmx=3D65534 kern.maxusers=3D1024 mlx4en_load=3D"YES" net.fibs=3D2 net.inet.tcp.hostcache.cachelimit=3D"0" net.inet.tcp.tcbhashsize=3D65536 net.inet.tcp.tso=3D0 net.isr.bindthreads=3D0 nmdm_load=3D"YES" vfs.zfs.arc_max=3D"36G" vfs.zfs.txg.timeout=3D"5" vfs.zfs.write_limit_override=3D"536870912" vfs.zfs.write_limit_override=3D"536870912" vmm_load=3D"YES" zfs_load=3D"YES" One possible culprit is vfs.zfs.arc_max is set to size of phys memory. I am adjusting that to half memory and rebooting. --=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-231457-227-S1sTOxDyQp>