I am curious now. Do you have a source for Backblaze?
This is the most infamous one Fatal: number of used blobs is larger than number of available blobs! · Issue #3268 · restic/restic · GitHub
(And subsequent comment about “we only fixed files that were reported by support tickets”… Production storage service my ass. “if you continue seeing a problem let us know” – how about implement monitoring and verification?)
This shit (returning bad data to customers) should have been impossible on that product maturity stage.
(This post summarizes pretty well other shit backblaze does without batting an eye: Frankly, I’ve never seen a good take from Backblaze once I got past their market... | Hacker News (and their rebuttal on the lack of zero-knowledge encryption is full of shit – you cannot restore encrypted data from backblaze business backup service without giving them your keys)).
Just don’t use Backblaze. Don’t cheap out on your data storage quality and integrity. You get what you pay.
(I can also pour a bucket of shit on ProtoCase that manufactures their storage pods, and its subsidiaries – 45Drives and 45HomeLab… but that’s for another day)
To stay somewhat on topic – the horrific swarm of nonsense companies like Backblaze, iDrive, pCloud, and other “budget” participants in the race to the bottom makes Storj’s quality, reliability, attention to details, and how fast they do fix reported failures stand out even more; vast majority of the complaints about storj are all cosmetic and pretty much irrelevant in the grand scheme of things, and I’m yet to see data integrity issue. Keep up the good job folks. (See, my buckets of shit sometime carry honey. Rarely, but it happens)
10 Likes
You know, this makes me even more curious. What actually does uplink do if the first 29 pieces’ erasure coding scheme errors out? I think the logic is here, but I’m too tired right now to untangle this.
Well, the comment there says
// just start over now
Good enough strategy for such a corner cases if you ask me 
1 Like
Yeah, but I think by the time this point is reached, 30th piece may show up as well. So, not sure (-:
Now I kinda want a forum account named “30thPiece”. Always a day late, and a dollar short…
4 Likes
I love the idea! I can imagine a snarky megahal-style AI bot that shows up from time to time to leave a sarcastic comment.
Story time. I used to attend an IRC channel where we had a young, but ambitious participant often participating in some more philosophical discussions, giving his strong opinions on various matters. At some point I trained megahal on his messages. The results were hilarious, and from time to time we even thought it could be a realistic message from that guy.
Yeah, I’d support a bot like that! I think @arrogantrabbit would be the perfect source of training data.
2 Likes
It should request another portion (or even all remained 
), I believe I saw some modifications regarding retries, but we definitely need to have at least a minimum required amount of healthy pieces of that segment to be able to reconstruct it.
In this case it would be - You got an extra piece but a token short.
mine started growing some weeks ago, must be customer activity. my node is from 2023.
2 Likes