"Out of memory" and "shfs: cache disk full" errors

[unRaide]

The Fix Common Problems plugin has been notifying me of "Out of memory" errors and I've also noticed that my logs are filled with "UnRaider shfs: cache disk full" errors.

 

Not sure what the issue is and hoping someone can help.

unraider-diagnostics-20240910-2214.zip

[itimpi]

The "UnRaider shfs: cache disk full" messages will be because the free space on the 'cache' pool is less than you have set for the Minimum Free Space setting so is informing you that a file is by-passing the cache.

[Michael_P]

4 hours ago, unRaide said:

been notifying me of "Out of memory" errors

 

Crashplan is running the host OOM, check its config and/or limit its RAM usage. Restart the server to clear the log or FCP will continue to warn you about the past events.

[unRaide]

8 hours ago, itimpi said:

The "UnRaider shfs: cache disk full" messages will be because the free space on the 'cache' pool is less than you have set for the Minimum Free Space setting so is informing you that a file is by-passing the cache.

Thx @itimpi! I checked this setting for my cache and it's set at 100KB and I currently have 69GB free?

[unRaide]

6 hours ago, Michael_P said:

 

Crashplan is running the host OOM, check its config and/or limit its RAM usage. Restart the server to clear the log or FCP will continue to warn you about the past events.

Thx @Michael_P! I checked my container and reduced the max memory from 6G to 4G (hopefully that's still enough). Although I've had it set to 6G for years, not sure why it's complaining now - perhaps other containers I've added have led to maxxing out my memory?

[Michael_P]

2 hours ago, unRaide said:

perhaps other containers I've added have led to maxxing out my memory?

Crashplan was using ~11GB when it was killed

[unRaide]

2 hours ago, Michael_P said:

Crashplan was using ~11GB when it was killed

Whoa, that’s crazy! Do you know how the container was able to exceed/bypass the 6G limit I added to the extra parameters?

Is there another way to enforce the memory used?

[Michael_P]

14 hours ago, unRaide said:

Do you know how the container was able to exceed/bypass the 6G limit I added to the extra parameters?

No, I don't know how docker determines when to enforce it or not - you can force docker to do it instead of the kernel with the --oom-kill-disable flag, but use it cautiously as it's highly likely to bring down the entire system if docker doesn't do it right.

 

https://docs.docker.com/engine/containers/resource_constraints/

 

Your best bet is to figure out why crashplan is running away and change its config to prevent it.

[unRaide]

On 9/11/2024 at 12:10 AM, itimpi said:

The "UnRaider shfs: cache disk full" messages will be because the free space on the 'cache' pool is less than you have set for the Minimum Free Space setting so is informing you that a file is by-passing the cache.

Thx @itimpi! Not sure if I'm still misunderstanding how this works but stopping the array and changing my Minimum Free Space to 4G instead of the 100KB is was seemed to do the trick. I felt as if the original setting should've worked but perhaps something else was going on  🤷‍♂️.