Kata1yst

Yeah honestly no idea regarding moderation. But the codebase is maintained by a team.

There is a team, not a sole dev.

I’m not saying everything is roses and rainbows, but this is FUD messaging being spread openly by the mbin dev team.

I’ve had great experiences with exactly one vendor of second hand disks.

https://serverpartdeals.com/

Currently running 8x14TB in a striped & mirrored zpool.

Really all I do is setup fail2ban on my very few external services, and then put all other access behind wireguard.

Logs are clean, I’m happy.

Yeah, you should be scrubbing weekly or monthly, depending on how often you are using the data. Scrub basically touches each file and checks the checksums and fixes any errors it finds proactively. Basically preventative maintenance.
https://manpages.ubuntu.com/manpages/jammy/man8/zpool-scrub.8.html

Set that up in a cron job and check zpool status periodically.

No dedup is good. LZ4 compression is good. RAM to disk ratio is generous.

Check your disk’s sector size and vdev ashift. On modern multi-TB HDDs you generally have a block size of 4k and want ashift=12. This being set improperly can lead to massive write amplification which will hurt throughput.
https://www.high-availability.com/docs/ZFS-Tuning-Guide/

How about snapshots? Do you have a bunch of old ones? I highly recommend setting up a snapshot manager to prune snapshots to just a working set (monthly keep 1-2, weekly keep 4, daily keep 6 etc) https://github.com/jimsalterjrs/sanoid

And to parrot another insightful comment, I also recommend checking the disk health with SMART tests. In ZFS as a drive begins to fail the pool will get much slower as it constantly repairs the errors.

ZFS is a very robust choice for a NAS. Many people, myself included, as well as hundreds of businesses across the globe, have used ZFS at scale for over a decade.

Attack the problem. Check your system logs, htop, zpool status.

When was the last time you ran a zpool scrub? Is there a scrub, or other zfs operation in progress? How many snapshots do you have? How much RAM vs disk space? Are you using ZFS deduplication? Compression?

It can. Most people just use the filesystem watcher, but this looks nice. https://github.com/deathbybandaid/tdarr_inform

Highly recommend using tdarr. Not just because the radarr container won’t do it, but because tdarr is so incredibly powerful.

I’ve had excellent luck with Docspell. https://github.com/eikek/docspell

GitLab and GitHub were always developed separately by completely different people and have never shared code.

SearxNG is still here to help

Yes, PodcastRepublic has a nearly perfect implementation. I have gotten so reliant on it I feel stuck here :)

Thank you for considering!

I’m desperately hoping some self hosted solution will implement multiple prioritied playlists (e.g all podcasts from feed X go to the priority 1 playlist, the main queue plays all priority 1 playlist entries before automatically proceeding to the next highest priority playlist etc).

I know it’s a long shot, but if you find any time in your already impressive roadmap it will be an instant conversion for myself and hopefully a few other weirdos.

I use a single unified traefik to front all of my services, no matter how they ship. Despite the slight overhead, it’s closer to a truly idempotent architecture. I’ve unfortunately had to test that twice now in my selfhosting career.

Traefik is very solid and I’ve had very few issues with it I didn’t self inflict. Documentation is very thorough.