3 ms·
I'm pretty sure this is an example of 'Silent Data Corruption' on something like the record length logic/variable causing it to return the next record in additi
by andromeduck 4y ago
I'm pretty sure this is an example of 'Silent Data Corruption' on something like the record length logic/variable causing it to return the next record in addition to the first.
I suspect if you look at the unexpected text, you'll find it'll be pretty close to a power of two or attributable to a single bit error in whatever processor logic that calculated it.
https://support.google.com/cloud/answer/10759085?hl=en https://support.google.com/cloud/answer/10759085?hl=en
- consumer451 4y agoThank you. I have been thinking about this since I posted, and the one thing I was sure of is that it was pretty far down the stack. Half halfheartedly, I was guessing it was something like a rare multi cosmic ray bitflip or something. From your link: > Today, many Google Cloud services contain such checks, thus preventing SDC errors from permanently corrupting customer or system data. It's interesting that it can still happen from one bit in a system like Google's storage for search. I guess that would probably be expensive?