Assuming the info in this link is correct, ZFS is using ~20GB for caching which makes htop’s ~8GB of in use memory make sense when compared with the results from cat /proc/meminfo. This is great news.
My results after running cat /proc/spl/kstat/zfs/arcstats:
c 4 19268150979
c_min 4 1026222848
c_max 4 31765389312
size 4 19251112856
Thank you for the detailed explanation
You’re an angel. I don’t know what the fuck htop is doing showing 8GB in use Based on another user comment in this thread, htop is showing a misleading number. For anyone else who comes across this, this is what I have. This makes the situation seem a little more grim. I have ~2GB free, ~28GB in use , and of that ~28GB only ~3GB is cache that can be closed. For reference, I’m using ZFS and roughly 27 docker containers. It doesn’t seem like there is much room for future services to selfhost.
MemTotal: 30.5838 GB
MemFree: 1.85291 GB
MemAvailable: 4.63831 GB
Buffers: 0.00760269 GB
Cached: 3.05407 GB
That’s pretty much where I’m at on this. As far as I’m concerned, if my system touches SWAP at all, it’s run out of memory. At this point, I’m hoping to figure out what percent of the memory in use is unimportant cache that can be closed vs important files that process need to function.
Is there a good way to tell what percent of RAM in use is used by less important caching of files that could be closed without any adverse effects vs files that if closed, the whole app stops functioning?
Basically, I’m hoping htop isn’t broken and is reporting I have 8GB of important showstopping files open and everything else is cache that is unimportant/closable without the need to touch SWAP.
This is why I’d like to know what tool shows the most useful number. If I only have 4GB out of 30GB left, is that 26GB difference mostly important processes or mostly closable cache? Like, is htop borked and not showing me useful info or is it saying 8GB of the 26GB used is important showstopping stuff?
Fuck. This is a bad time to be running low on memory
I didn’t realize it was that old. Whoever is maintaining it is doing a good job making it look modern
NetNewsWire - free, open source, FreshRSS integration
This looks cool but only having 5 bays is a dealbreaker. I want a minimum of 6 for a Raid-Z2 setup.
Docker has been the deployment method of choice…
Nice 😎
I’m not attached to either, I’ve seen a lot of people recommend them. Debian has gotten more than a few recommendations in this thread, so I’m checking out PikaOS now.
The biggest problem you are going to have is the NVIDIA graphics card. As long as you overcome the hurdle of installing those drivers, any of the popular desktop OSs should be fine. Some people seem to get them going no problem but for others, it’s a show stopper. The OSs that have the option for installing the drivers during installation are nice for that reason.
As much as I didn’t want to, it’s really seeming like I’m going to need to pick a few a test them out…
Yeah. Unfortunately that’s going to be the best way to learn what you want from your OS. It’s equally frustrating and rewarding.
Is it common practice to use one FS across all drives? Or would ZFS work well enough on its own for the pool and use a different FS for the OS/storage drives?
Depends on the environment, really; there’s no wrong answer. ZFS will work fine for its own pool. I would say a FS with snapshotting and rollback capabilities are almost a requirement for Arch based/rolling release distros. You never know when an update might break something.
I’ve been testing out ZFS on my OS drive for my personal server and it’s probably overkill because all the important stuff is on the ZFS pool with backups. My OS drive could shit the bed at any moment and I could switch it out with anything else because of that pool.
It’s being used as a Jellyfin+arr stack, qbit, Immich
for those applications any distro that lets you use docker and docker compose. If you don’t know how to use them, do yourself a favor and learn. It makes self-hosting so much easier and makes the base OS almost irrelevant.
Is Bazzite going to be too tinker-proof, or is CachyOS just way too much work?
Since you seem set on these two, go with Bazzite. Between Distrobox and Docker, Bazzite being an immutable OS seems like a non-issue. After you play around with it, if you feel like you want something that could potentially require more of your time but gives you a little more control, go with CachyOS but ensure you are using ZFS, btrfs, or some other file system that allows rollbacks.
I’ve distro-hopped a lot over the years. Ubuntu (most flavors), Fedora, Debian, Arch, Solus, EndeavourOS, CentOS, Alma, more I’m forgetting, and even some BSDs. Out of all of them, I keep going back to Ubuntu for my servers. I like the release cycles, it’s never given me any issues that I didn’t cause myself, the packages are new enough, the installer lets you set up ZFS and 3rd party tools/software (like Nvidia drivers), and there is a ton of documentation. I want my server to be an appliance, not something I tinker with, and Ubuntu does that really well. If I do feel like tinkering, I do it in a VM or container.
You’re silly
I think your post breaks rule 4 for trolling but you’ve made a good point 🤷♂️
Agreed. Debian with docker, flatpak, and/or distrobox is solid
I think I see what you’re saying. My gripe is that if I want a laptop/tablet with a great ARM chip, with long battery life, my options all force me to use one of two operating systems that I’d prefer not to use for ideological reasons. If I’m forced to use one, because I want an ARM device, I might as well use the one that has the best hardware. M5s are right around the corner and the MacBook Airs are really competitive.
If I misinterpreted your question, then no, as far as I’m aware, none of the M series has FULL support. The M1s and M2s are pretty close though.
Let me know when these X elite chips have full Linux compatibility and then I’ll be interested. Until then, I’ll stick with Mac, it has the better hardware.
deleted by creator
Just to add to your comment; get a three phase inspection. Inspect the foundation before the walls go up, inspect right before the drywall goes up, and inspect after the drywall goes up before you start signing paperwork. If you wait to inspect after the drywall is up, you can miss a lot.
Came across some more info that you might find interesting. If true, htop is ignoring the cache used by ZFS but accounting for everything else.
link