Very interesting that a read operation manages to corrupt the index. That makes it likely that it causes an overflow or similar memory corruption in an unfortunate place while reading. For example allocating a buffer based on the literal length of that path and then later expanding the variable?
I’m not sure it actually does corrupt anything. I just spent an hour on this and it never manifests itself as any actions performed via chkdsk. I think it might just trigger a mandatory consistency check.
5 comments
[ 3.3 ms ] story [ 26.3 ms ] thread