The issue with diagnosing memory issues is that it usually results in no memory available to handle the logging of such a problem when it happens.

I’ve found that the easieat approach is to set up a file as additional swap space, and swapon, then see if the problem disappears, either partially or fully.

Personally I’d just upgrade to RAIDZ2, and add as many disks to that as reasonably practical. To be honest, I fail to see any downsides to using four disks for this other than the storage inefficiency.

rsync?

You’ll probably be fine with hetzner. If not, you can cancel whenever.

I have moved over to inhouse hosting, but I exclusively used hetzner for years, a lot of it via the auction.

If you don’t need something very specific, the auction is a great way to spin up something cheaply.

I’m not very well versed on docker, but this sounds like a config issue. The behavior seems similar to “squash root” found in many other services.

deleted by creator