Thanks for answering! But I did not found in the paper anything really related to what I was asking, regarding high latency (on the storage side) and corruption of data manipulated by applications such DBs and virtual machines.
Can you point what exactly what caught your attention?
Sorry, maybe I miss understood then? disregard that link.
Just thinking out loud here... part of that slow latency is getting the ACK back to the client/host that requested the write, right? Host sends -> <travel time> -> storage gets -> storage writes -> storage sends the ACK back -> <travel time> -> host gets the ACK and knows the data is good.
Could 30ms latency directly cause an issue... maybe? Maybe if a client/host went offline during that small windows between storage ACK and the host getting the ACK? But is 30ms latency an issue with databases.... I'd go with yes.
We had a case opened withe NetApp. First NetApp asked us to replace IOXM and SAS adapter. It did not solved the issue. Lastly, as a last resort, replacing motherboard module did the trick. Even though there was not a specific error or anything else pointing to the MB, it was it.