VN Ren'Py Artemis [v0.6.1b] [digi.B]

[ishindenshin]

It's the same core problem, there's zero redundancy. If the drive your shit is on goes tits-up, that's complete data loss. That's fine for stuff that's not important, but if it's only being stored in one place, you're just asking for it.

If my media library drive blows up, while annoying, it's at least being mirrored to other locations (offsite), so I can still do a recovery if necessary. I miss my proper RAID5 array, though.

Just because a JBOD doesn't come with any sort of hardware redundancy doesn't mean it can't have some software one. It's the optimal hardware situation for some ZFS pool or something equivalent (unraid, etc). It comes with some benefits on top (no write-hole, volume and snapshot management, compression, deduplication, etc). You can totally use it to mirror your data across multiple disks, or / and mimic a raid5 array with a raidz1, or add more redundancy with a z2 (equivalent of a raid6) or even a z3 for up to 3 disk failures.

Check it out.

 

[Maccabbee]

Just because a JBOD doesn't come with any sort of hardware redundancy doesn't mean it can't have some software one. It's the optimal hardware situation for some ZFS pool or something equivalent (unraid, etc). It comes with some benefits on top (no write-hole, volume and snapshot management, compression, deduplication, etc). You can totally use it to mirror your data across multiple disks, or / and mimic a raid5 array with a raidz1, or add more redundancy with a z2 (equivalent of a raid6) or even a z3 for up to 3 disk failures.

Check it out.

Most home JBOD devices don't offer that level of resiliency. RAID 6 or RAID 10 (hardware implemented) is still the best for performance and resiliency, but not great with SSDs, as it impacts their lifecycle negatively.