Comment 238 for bug 1470250

FYI, When I did the analysis of this last year I found a couple of additional key data points that may help with reproducing the error. I reported them at the time but they're well buried by now.

1) Timing of the bug appears to be load related. I found that generating the error could take minutes, hours, days or even weeks, depending on load. To generate the error faster, try putting significant I/O and CPU load on the Hyper-V server, especially I/O. I don't have my notes in front of me but I recall that I/O load had the highest influence.

2) RHEL / CentOS is not immune, it just manifests differently. On RHEL/CentOS, at the same time as Ubuntu generates the file system error, RHEL/CentOS will have a large (400ms - ~5000ms) latency in I/O. On RHEL/CentOS it's just that no file system error occurs.

Hope that helps.