this post was submitted on 11 Feb 2026
29 points (89.2% liked)
Jellyfin: The Free Software Media System
8636 readers
1 users here now
Current stable release: 10.11.6
Matrix (General Information & Help)
Matrix (Off-Topic) - Come get to know the team and blow off steam!
Matrix Space - List of all the available rooms on Matrix.
Discord - Bridged to our Matrix rooms
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Rebuilding parity requires processing power. Copying a mirror does not.
There's also the fact that the rebuild stresses the drives, increasing the chance of a cascade failure, where the resulting rebuild after a drive failure, reveals other drive failures.
It all results in management overhead, which having to "just tweak some parameters" makes worse, not better.
In comparison to simple mirroring and backing up offsite, RAID is a headache.
The redundancy it provides is better achieved in other ways, and the storage pooling it provides is better achieved in other ways.
That shouldn't be an issue with any NAS bought in the past decade.
You can tweak the parameters so the rebuild is being done slower. Also, mirroring a disk stresses the (remaining) disk as well. (But to be fair, if that one fails, you'll still be able to access the data from the other mirror-pair(s).)
I'm not seeing that. Tweaking parameters is not necessary unless you want to change the default behaviour. Default behaviour is fine in most cases.
Speak for yourself. I rather enjoy the added storage capacity.
So do I.
It's just that I use btrfs, mergerfs, or lvms to pool storage. Not RAID.
Making changes to my storage setup is far easier using these options, much more so than RAID.
Mergerfs especially makes adding or removing capacity truly trivial, with the only lengthy processes involved being bog-standard file transfers.
Hard drive storage is pretty cheap. And the effort it takes to make changes to a raid volume as my needs change over the years, just isn't worth the savings.
How often do you change your storage setup? I've configured everything once like 5 years ago and haven't touched it since. I can add larger disks in pairs and the Synology does some LVM-/mdraid-magic to add the newly available free space as RAID1 until I add a third larger disk and it remodels it to RAID5.
How do you handle parity with MergerFS? Or are all your storage partitions mirrored?
Not really - especially, if you're looking for CMR drives. And any storage increase needs at least 2 disks with basically no (ethical) way to get any money back for the old ones.
Every year or so.
My NAS is self-built.
I used to buy one more drive whenever my pools would start getting full. I'm now in a place where I can discard data about as fast as I get more to store, I don't predict needing new drives until one fails.
I've re-arranged my volumes to increase or decrease parity many times after buying drives or instead of buying drives.
Mergerfs makes access easy, the underlying drives are either with or without parity pairs, and I have things arranged so that critical files are always stored with mirroring, while non-critical files are not.
Interesting! Thank you for that insight. I might adopt some methods for when I finally replace the Synology with a new NAS (which will definitely not be another Synology device!).