I'm playing around with systemd-homed over samba/cifs.

At some point I started searching for "tune samba performance," and found sites like this.

I had my config looking something like,

[global]
socket options = TCP_NODELAY IPTOS_LOWDELAY
read raw = Yes
write raw = Yes
strict locking = No
oplocks = yes
dead time = 15
getwd cache = yes
aio read size = 16384
aio write size = 16384
use sendfile = true

It seemed like any time my system used any SWAP it would hang.

In tty1 it would show a bunch of lines like 'watchdog ... CPU# stuck...' have a line talking about OOM killer, then repeat more watchdog lines. The only way to get it out seemed to be a hard reset.

I ran a Memtest and it came back with a Pass.

Now that I've removed those lines the machine seems to be stable again. I also moved the samba server to a raspberry Pi.

I was originally running it on a Ubuntu 23.04 fairly standard PC, i3-4150, 16GB RAM.

I searched around and only found one or two forum posts about the samba server hanging, which seem unresolved. They didn't post their config.

Apparently the solution is: Just don't use those settings!

My Question: I'm not crazy right? This is possible? It seems like one or more of these samba settings was causing my system to eventually hang? I added them and had problems, removed them and system hasn't hung since.

Does anyone know enough samba to know why that would absolutely crush my PC?

Thanks for reading.

Edit: [Screams] Okay, maybe it wasn't samba because it just hung two hours ago.