ZFS also directly addresses this issue in that a scrub can be setup in cron, which will detect any data issues and send email. One could do that with smartctl too, but that can be too late, where a ZFS scrub is more likely to let you know of issues before data loss.

Not this this helps you, but it’s been running solid here since upgrading. I’d take a look at the logs and see what’s going on, myself.

Definitely. As much as a centralized /c namespace is against all the principles of a decentralized system, lack of a centralized namespace results in topical duplication and hinders discovery. I don’t know how, but seems to me some sort of happy medium has to fall out.

I never had much luck with the layout editors, so I just hand edit the JSON. Here’s part of my main dashboard (it scrolls on for a ways, but this much was already a big screenshot).

I use Manjaro, but I run it like vanilla Arch (for example pacman/yay and not pamac). I find this to be a sweet spot for me - rolling releases are so incredibly nice, and Manjaro being slightly slower than Arch is good from a stability standpoint in my experience.

I use ZFS all over the place, including the root storage pool on my home server, which has overall been a great experience with systemd-boot.

Doesn’t help you, but I haven’t seen this issue - I recently upgraded to 2023.6.1.

i3 is what I’ve been using the past few years. I’ve tried others, but I always end back up with i3 as I’ve found nothing else to be as simple and efficient for my workflow, with 12 workspaces across 2 monitors.