btw, i'm just wondering, unRAID basically is kind of JBOD, right? when you have a set of disks (user share), the data will be written on disk by disk, it will only go to the next disk when the first gets full, right?

 

Mod note: Split from the 4 TB thread for being off-topic

- Raj

 

ok.

 

btw, i'm just wondering, unRAID basically is kind of JBOD, right? when you have a set of disks (user share), the data will be written on disk by disk, it will only go to the next disk when the first gets full, right?

 

There are several allocations methods available within unRaid, and you can even assign certain disks to be used only by certain shares.  You can do a semi-load share, for example, where it will go back-and-forth and fill up both disks generally equally, etc...

 

What you describe -- fill up one disk, then go to the next, is just one of many combinations.

 

And on top of it is "split-level" where you can specify to keep all the "files for a given directory" together (like all the files that make up a DVD) so that you don't have a lag for another drive to spin up at playback time.

In addition it's more than jbod because it is protected via a parity disk

I like to consider it a Protected JBOD.

Each disk exists individually as a disk and filesystem protected by a parity drive.

There is a software layer that combines them virtually to be seen individually or together as a collection.

A true...

Redundant Array of INDIVIDUAL Disks!