After upgrading to FreeNas 8.2, the system started to freeze

[prostup]

Hello everyone,

Recently I upgraded the server to 8.2 and the system started to freeze a lot, then I upgraded the memory from 4GB to 8GB and re installed to 64bit system and I'm still having troubles with it.

This is the latest error I got:
freenas afpd[36771]: sys_getextattr_size: error: Result too large
panic: kmem_malloc(131072): kmem_map too small: 540434432 total alocated
cpuid = 1
Uptime: 4d10h20m52s

other system related info:
Build FreeNAS-8.2.0-RELEASE-p1-x64 (r11950)
Platform Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz
Memory 8090MB

Is there anyone who can help me to resolve this problems?

Where can I find a log file to see how was the server performing before crash? Why there is only reports since last reboot?

Where can I find a list of FreeNAS errors with explanations?

Thanks,

 

[William Grzybowski]

Did you enable autotune? If so, disable it.

Have entries in Sysctls/Tunabled related to memory? Delete them.

 

[prostup]

Thanks William,

1. I disabled the auto tune...
2. All entries in Sysctls and Tunables was generated by autotune and I disabled only following entries in Tunables: vm.kmem_size_max and vm.kmem_size_max

Is it enough to disable it or I really need to delete it?

Here are all entries now:

Sysctls:
Variable Value Comment Enabled Available actions
net.inet.tcp.sendbuf_max 2097152 Generated by autotune True Edit Delete
kern.ipc.maxsockbuf 2097152 Generated by autotune True Edit Delete
net.inet.tcp.recvbuf_max 2097152 Generated by autotune True Edit Delete

Tunables:
Variable Value Comment Enabled Available actions
vfs.zfs.arc_max 536870912 Generated by autotune True Edit Delete
vm.kmem_size_max 701448320 Generated by autotune False Edit Delete
vm.kmem_size 561158656 Generated by autotune False Edit Delete
kern.ipc.nmbclusters 5000 Generated by autotune True Edit Delete

Thanks again,

Joseph

 

[William Grzybowski]

You can disable vfs.zfs.arc_max as well, or even low it down a bit more if you're still experiencing panics...

You need to reboot so they can take effect...

Make sure they dont appear in /boot/loader.conf or /boot/loader.conf.local

 

[prostup]

Just did it... waiting for reboot and probably another few days to find out if that works...
Thanks...