Why does more than one drive activity light flicker when watching a movie? Also, if it isn't striping data, how does it achieve parity that works? Logic would dictate if it isn't striping data, to actually achieve parity you would need a raid 1 setup with mirroring for it to actually protect your data.
My thought is this...you have 2 parity drives and 8 pool drives. Your parity drives are 3tb each, and your pool drives are 3tb and 2tb mixed. You have say...15tb of 17tb populated. One of your drives craps out. How do you actually guarantee that all of the information on the drive that died is available to be rebuilt from your parity drives? You lost 3tb of data and your parity drives only hold a max potential of 6tb, assuming no overlap in parity storage.
If it isn't striping (even if it isn't "live" striping and only on a snapshot), then how can they even call it a parity drive?
The whole point of parity is that all your information is duplicated in a redistribed fashion on multiple drives so that if one dies, the information is still spread out on the other drives and everything on the dead drive can be rebuilt.
From what I understand you are saying, your information in fact is NOT in parity like raid 5 (one drive parity) or raid 6 (two drive parity) would dictate. So...why even bother with parity in flexraid if it does not stripe? Logic would dictate unless you have the same amount of storage dedicated to your parity drives as you have dedicated to your storage drives, your information is constantly at risk...
So...why bother with parity in flexraid at all if it isn't parity?
With a hardware driven raid 6 array, similar to my example, you would have 8 data and 2 parity drives...all of them would be written to in a stripe with data being written twice on at least 2 different drives, so if one or two fail, all the data can be recovered. I assumed (wrongly it seems) that flexraid duplicated this pattern when you activated a snapshot parity calculation.
I'll be looking for another solution for drive pooling if this is actually the case. It offers no protection once you pass the storage capacity on the "parity" drive, which is stupid and pointless.
ETA I'm retarded and was thinking it was using a raid 4 parity structure for a software raid 6. I also lick windows on the shortbus when my helmet isn't on tight enough.