36
Has anyone messed around with NonRAID? (github.com)
submitted 1 year ago by to c/selfhosted@lemmy.world
10 comments fedilink hide all child comments
 

I just found this project by browsing the mergerfs documentation. It claims to be an opensource fork of the Unraid software that makes it so flexible. The documentation isn't great, but has all the basic info to get going. It works kinda like Snapraid in that each disk has it's own filesystem and parity is calculated across all of the drives, but it happens in real time (unlike with snapraid).

Thoughts? comments? Would you trust this with important data?

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 1 year ago (6 children)

What is the gain compared to running something battle tested like zfs or mdraid?

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 10 points 1 year ago (5 children)

    The selling point of unraid is that you can mix and match different disk sizes and it figures out a (good, efficient?) way to handle them even as you grow a pool. You're not going to have a good time with a 1TB drive, a 2 TB drive and a 15 TB drive using zfs, unraid doesn't care... (Using and preferring zfs myself, by the way; this is heresay.)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] [S] 4 points 1 year ago

    Another benefit is if you lose your all parity disks and a data disk, you can still access the filesystem on the other data disks. So if the array fails, you don't lose all the data, just the 1 (failed) disk worth of files.

  • permalink
  • fedilink
  • source
  • parent