Lost Shares / Out of Memory Errors 6.4.1

[alig26]

Hello All,

Been having this problem for the past few weeks, where I lost my shares, and when I look at the logs I'm getting Out of memory errors:

I've also attached the the Diagnostic logs.

 

Unraid has 8GB of ram, and it's been running great for years, would adding another 8gb of ram solve my problem?

 

Thanks

eb 26 08:35:33 unraid kernel: Out of memory: Kill process 4798 (shfs) score 724 or sacrifice child
Feb 26 08:35:33 unraid kernel: Killed process 4798 (shfs) total-vm:6610696kB, anon-rss:6072380kB, file-rss:4kB, shmem-rss:592kB
Feb 26 08:35:33 unraid kernel: oom_reaper: reaped process 4798 (shfs), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Feb 26 08:35:33 unraid kernel: nfsd: non-standard errno: -107
Feb 26 08:35:33 unraid kernel: ------------[ cut here ]------------
Feb 26 08:35:33 unraid kernel: WARNING: CPU: 2 PID: 4190 at fs/nfsd/nfsproc.c:810 nfserrno+0x4a/0x50 [nfsd]
Feb 26 08:35:33 unraid kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat reiserfs xfs nfsd lockd grace sunrpc md_mod e1000e ptp pps_core ipmi_ssif x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel cryptd mvsas intel_cstate libsas i2c_i801 intel_uncore i2c_core ahci intel_rapl_perf libahci scsi_transport_sas video backlight thermal button fan ipmi_si [last unloaded: pps_core]
Feb 26 08:35:33 unraid kernel: CPU: 2 PID: 4190 Comm: nfsd Not tainted 4.14.16-unRAID #1
Feb 26 08:35:33 unraid kernel: Hardware name: Supermicro X9SCL/X9SCM/X9SCL/X9SCM, BIOS 2.0a 06/08/2012
Feb 26 08:35:33 unraid kernel: task: ffff880215e44600 task.stack: ffffc90000f54000
Feb 26 08:35:33 unraid kernel: RIP: 0010:nfserrno+0x4a/0x50 [nfsd]
Feb 26 08:35:33 unraid kernel: RSP: 0018:ffffc90000f57da0 EFLAGS: 00010286
Feb 26 08:35:33 unraid kernel: RAX: 000000000000001e RBX: 0000000005000000 RCX: 0000000000000000
Feb 26 08:35:33 unraid kernel: RDX: ffff88021fd1d101 RSI: ffff88021fd16478 RDI: ffff88021fd16478
Feb 26 08:35:33 unraid kernel: RBP: ffff880183b3b024 R08: 0000000000000003 R09: ffffffff81feeb00
Feb 26 08:35:33 unraid kernel: R10: ffffc90000f57db0 R11: 0000000000000040 R12: ffff880183b3b020
Feb 26 08:35:33 unraid kernel: R13: ffff880212bf3c08 R14: 000000000000001c R15: ffffffffa00ca0e0
Feb 26 08:35:33 unraid kernel: FS:  0000000000000000(0000) GS:ffff88021fd00000(0000) knlGS:0000000000000000
Feb 26 08:35:33 unraid kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 26 08:35:33 unraid kernel: CR2: 00001554ea91e490 CR3: 0000000001c0a005 CR4: 00000000000606e0
Feb 26 08:35:33 unraid kernel: Call Trace:
Feb 26 08:35:33 unraid kernel: encode_post_op_attr.isra.2+0x59/0xa1 [nfsd]
Feb 26 08:35:33 unraid kernel: nfs3svc_encode_readres+0x18/0xb9 [nfsd]
Feb 26 08:35:33 unraid kernel: nfsd_dispatch+0x126/0x161 [nfsd]
Feb 26 08:35:33 unraid kernel: svc_process+0x3df/0x634 [sunrpc]
Feb 26 08:35:33 unraid kernel: ? nfsd_destroy+0x5a/0x5a [nfsd]
Feb 26 08:35:33 unraid kernel: nfsd+0xf4/0x14b [nfsd]
Feb 26 08:35:33 unraid kernel: kthread+0x111/0x119
Feb 26 08:35:33 unraid kernel: ? kthread_create_on_node+0x3a/0x3a
Feb 26 08:35:33 unraid kernel: ? do_group_exit+0x95/0x95
Feb 26 08:35:33 unraid kernel: ret_from_fork+0x35/0x40
Feb 26 08:35:33 unraid kernel: Code: 1c d5 e0 99 0c a0 eb 25 80 3d fa 09 01 00 00 bb 00 00 00 05 75 17 89 fe 48 c7 c7 ab a7 0c a0 c6 05 e3 09 01 00 01 e8 8c 06 fc e0 <0f> ff 89 d8 5b c3 48 83 ec 10 48 8b 87 90 00 00 00 31 c9 ba ff 
Feb 26 08:35:33 unraid kernel: ---[ end trace 9a60d5d31ffb8bd1 ]---

unraid-diagnostics-20180226-1057.zip

[Frank1940]

You can try this as it has fixed OOM problems for a lot of folks:

 

https://lime-technology.com/forums/topic/58855-regular-out-of-memory-problems/#comment-577424

 

And you might want to read this thread:

 

https://lime-technology.com/forums/topic/65720-shfs-memory-leak/

and this one:

https://lime-technology.com/forums/topic/69047-640-641-shfs-taking-a-lot-of-memory-~8gb-now/

 

[alig26]

Ahh thank you!

[awalkawalk]

I had these errors as well when upgrading to 6.4.1.  I have a X11SSM-F Supermicro motherboard but like you I was running the 2.0a BIOS version.  After upgrading to 2.0c I have had no errors at all and my shares have stayed online.