3 ms·
Very nice work, and thanks for releasing under MIT. Cheers. The hard work goes to BB, their initial library, though :) Interesting that Backblaze decided to g
by klauspost 11y ago
Very 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.