I have never seen something like this before.

This file is not in use by anything else on the system.

$ md5sum xppro.vdi
589cbb5501dcddda047344a3550aaa95 xppro.vdi
$ md5sum xppro.vdi
a69806ec60d39e06473edbb0abd71637 xppro.vdi

No errors on dmesg, no explanation for this. The behavior is repeatable - every invocation produces a different result. It behaves the same regardless of which partition I put the file on.

More details on my blog at http://changelog.complete.org/archives/7452-unreported-disk-data-corruption-kernel-bug . Any ideas for troubleshooting welcome, of course.
Shared publiclyView activity