3 ms·
Very nice work, and thanks for releasing under MIT. Interesting that Backblaze decided to go with 17+3 configuration. As I read more on the topic, I realized I
by zaroth 11y ago
Very nice work, and thanks for releasing under MIT.
Interesting that Backblaze decided to go with 17+3 configuration. As I read more on the topic, I realized I haven't quite wrapped my head around how data and parity are allocated across symbols, stripes, and disks, and how all that impacts degraded read performance, but at first glance I would assume 17+3 would have a pretty terrible degraded read performance.
Another great read if you're interested in home brew RAID or using parity is Plank's paper "Tutorial on Reed-Solomon Coding for Fault-Tolerance in RAID-like Systems". [1]
I found that gem reading Adam's blog on implementing triple parity RAID in ZFS. [2]
[1] - http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.103.7089&rep=rep1&type=pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.103...
[2] - https://blogs.oracle.com/ahl/entry/triple_parity_raid_z https://blogs.oracle.com/ahl/entry/triple_parity_raid_z
- klauspost 11y agoVery nice work, and thanks for releasing under MIT. Cheers. The hard work goes to BB, their initial library, though :) Interesting that Backblaze decided to go with 17+3 configuration. Yeah. It seems they don't go for any RAID within a storage pod, but instead uses raw ext4, and distributes shards across pods instead of hard drives in a single pod. [1] This would of course mean that a single pod isn't loaded when a drive is replaced, but it is distributed across 17 other pods. [1] https://www.backblaze.com/blog/vault-cloud-storage-architecture/ https://www.backblaze.com/blog/vault-cloud-storage-architect...
- haikubrian 11y ago(BrianB from Backblaze here) Yes, that's right. When a drive is replaced, its contents are rebuilt from the data on the 19 corresponding drives in the other 19 pods in the vault.