[Bug 231457] Out of swap space on ZFS

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231457

Mike <mikeowens at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mikeowens at gmail.com

--- Comment #1 from Mike <mikeowens at 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 at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC 
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="YES"
accf_http_load="YES"
autoboot_delay=3
cc_htcp_load="YES"
hw.igb.rx_abs_int_delay=1024
hw.igb.rx_int_delay=512
hw.igb.rxd=4096
hw.igb.tx_abs_int_delay=1024
hw.igb.tx_int_delay=512
hw.igb.txd=4096
hw.intr_storm_threshold=9000
if_bridge_load="YES"
if_tap_load="YES"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
kern.ipc.nmbclusters=262144
kern.ipc.nmbjumbo16=32768
kern.ipc.nmbjumbo9=65536
kern.ipc.nmbjumbop=262144
kern.ipc.semaem=32767
kern.ipc.semmni=32767
kern.ipc.semmns=8192
kern.ipc.semmnu=4096
kern.ipc.semmsl=120
kern.ipc.semopm=200
kern.ipc.semume=80
kern.ipc.semusz=184
kern.ipc.semvmx=65534
kern.maxusers=1024
mlx4en_load="YES"
net.fibs=2
net.inet.tcp.hostcache.cachelimit="0"
net.inet.tcp.tcbhashsize=65536
net.inet.tcp.tso=0
net.isr.bindthreads=0
nmdm_load="YES"
vfs.zfs.arc_max="36G"
vfs.zfs.txg.timeout="5"
vfs.zfs.write_limit_override="536870912"
vfs.zfs.write_limit_override="536870912"
vmm_load="YES"
zfs_load="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.

-- 
You are receiving this mail because:
You are the assignee for the bug.