I work with enterprise Storage systems like NetApp where disk storage is pooled into an aggregate and you can create volumes and LUNs from the aggregate.  Not having experience with unRAID before, I had expected more of a storage pooling system rather than the user share/split levels that are being used.

 

While I think it would be a neat feature to have in unRAID, I am not sure an aggregate style system would work with SATA drives.  ISCSI seems to be the default for more enterprise level systems do better I/O performance and disk seek/write operations.

 

I was wondering if aggregate style storage had ever been considered, and why it was/was not adopted or perhaps if this is a goal for the future.

 

Thanks,

 

D

 

 

If I understand you correctly then what you're asking about is not posible with unRAID. unRAID uses a number of individual disks. The share just makes the data on multiple individual disks appear as one big volume.

 

You need a striped array of some kind where multiple disks are basically combined into one larger disk/storage array to do what you ase asking about.

 

Peter

 

If I understand you correctly then what you're asking about is not posible with unRAID. unRAID uses a number of individual disks. The share just makes the data on multiple individual disks appear as one big volume.

 

You need a striped array of some kind where multiple disks are basically combined into one larger disk/storage array to do what you ase asking about.

 

Peter

 

 

Yes, it would essentially be data striping across the data drives, with the exclusion of the parity drive.  So there is still redundancy from single disk failure.

Striping on data disks may help with reads but writes will still be limited by the parity system.

You want to go find a RAID4, RAID5, RAID6, etc system then. Lots of solutions of that type if you really want to do that. unRAID was purposely created to not use striped arrays.

One reason for avoiding striping is that if more than one disk fails then only the files on the failed data disk(s) is lost. All other data disks contain readable files. Another reason is to facilitate the use of mixed drive types and sizes.