High RAM Usage and System Crashes with Samba Add-on on Home Assistant

Hello everyone,

I’m currently facing an issue with the Samba add-on on Home Assistant OS (using a Pi5 with 8G). When I try to transfer a large amount of data to the Home Assistant server, the Samba add-on seems to consume an excessive amount of RAM. As a result, my system eventually crashes due to the high memory usage.

Has anyone encountered this issue before, and are there any known workarounds or solutions to reduce the RAM consumption or manage large file transfers more efficiently with Samba?

I’m running the latest version of Home Assistant and the Samba add-on, and I’ve already tried restarting the system and optimizing configurations, but the issue persists.

Any help or advice would be greatly appreciated!

Thank you in advance!

PS: My current workaround via SSH: docker update --memory 800m --memory-swap 800m addon_core_samba (but i need to set it after each restart)

You may be in the actual need for a real computer my friend.

2 Likes

Maybe you’re right; however, I like the Pi 5 as is—it’s already small, and Home Assistant runs quite fast on it. It’s just the Samba issue that’s annoying… :worried: Is there an N100 or something similar in an equally small design, or do you have any suggestions for a tiny, sleek Mini PC that would work well as a home server?

Any other add-ons running? I’ve never had any problems with Samba (either on a Pi4 or a “real” computer) but things like Studio Code Server will eat away at system resources until there’s nothing left, even if you’re not using them.

2 Likes

That’s certainly true, but with glances I can see this Docker container is immediately maxing out my RAM when I write to or read from the SMB share:

Beelink has cheap stuff with more avail memory and options…

This issue have nothing to do with hardware.
It is how the OS or the Samba service is configured and if it is HAOS you are running, then switching the hardware will probably do nothing, since HAOS and the Samba addon should be configured similar, even though the hardware differs.

It sounds like HAOS is storing everything in ram when copying and do not make partial writes or use the swap partition.
I guess the author of the addon made it to access the config folder easily from a Windows machine and not as such for large file transfers.

Should this be resolved by Home Assistant itself, or is it something the provider of the Samba add-on should address? How could i create a bug note?

I can not pin point it further.
It is ages ago I configured a samba service and a Linux setup myself, so I can not say where the issue lay, but you do not see NAS systems with 32 Gb ram as standard and many of them run on Linux too with an ARM CPU.

It might be a “design” choice when making the addon though, but the author might tell you more.

Create an issue here: