this post was submitted on 08 Aug 2025
535 points (98.5% liked)
Technology
73807 readers
4096 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Coincidentally I no longer support windows machines in my home.
Just finished building a new PC last night, 64GB RAM, 8GB vRAM, 2TB m.2, 8x8TB HDD, and windows will never goddamn touch it. It feels weird, but so far so good.
Jellyfin. The HDDs were only ~$110 each. Seagate 5400s but w/e it's mass storage. No raid, drives will just be filled, cloned, and the clone dropped into a second system, also with no windows 🤬
Look at ZFS, it's a bit more intelligent about using the space. They'll be part of a pool of drives that you create 'datasets'(basically virtual drives) from and you can choose your level of redundancy (including none at all if you want to roll the dice there).
I have a 20TB array, 16TB available. It's already saved me from a lost disk. Using Seagate 5x 4TB 5400s also, with a NVME drive for the ZIL (speeds up writes). I have a 32GB ARC (a ZFS cache in RAM) so, even though the drives are slow the RAM and NVME drives ensure that it always feels snappy.
You can use zfs-send to clone the data to a new system without them having to have an exact copy of your original setup (like they would if you're using drive images). It is also a copy on write filesystem so it supports snapshotting (creating backups of the block level diffs, so it is very space efficient as it only stores the block-level changes to the file).
I don't believe you! (that it is coincidential)
:)