I'm seeing filesystem corruption issues since upgrading to Parallels 10 (Windows 7 guest OS).
I've managed to replicate the problem in a simple way:
- create a text file on the Windows volume
- edit that text file (I'm using vim) on the OSX host
- write the file. I get the error "this file has been modified since it was last written!" (this is Vim signaling that Something Is Wrong)
- load the file from disk again. It contains a corrupted version of the old and new versions of the file.
I can guarantee that vim isn't introducing this corruption, so there's definitely some filesystem wonkiness going on.
Immediately after my upgrade to Parallels 10, I noticed that a CAD program on the Windows side (Rhino) could no longer open files hosted in a Dropbox on the OSX host side (it could do so before the upgrade). This suggests to me that the filesystem corruption is bidirectional.
I've managed to replicate the problem in a simple way:
- create a text file on the Windows volume
- edit that text file (I'm using vim) on the OSX host
- write the file. I get the error "this file has been modified since it was last written!" (this is Vim signaling that Something Is Wrong)
- load the file from disk again. It contains a corrupted version of the old and new versions of the file.
I can guarantee that vim isn't introducing this corruption, so there's definitely some filesystem wonkiness going on.
Immediately after my upgrade to Parallels 10, I noticed that a CAD program on the Windows side (Rhino) could no longer open files hosted in a Dropbox on the OSX host side (it could do so before the upgrade). This suggests to me that the filesystem corruption is bidirectional.