VMPlayer/Ubuntu 上的 Eclipse 一直说我的文件在磁盘上已更改
受到开发人员使用虚拟机的成功案例的激励，我决定尝试一下。我在 WinXP 主机上的 Ubuntu 9.04 客户机上运行 Eclipse。由于主机上的网络驱动器每天备份两次，因此我决定与网络驱动器中的 VM 共享我的 Eclipse 工作区。
一切似乎都很好，除了在来宾 Eclipse 上经常弹出警告，指出文件系统上的文件已被修改，我可以更新编辑器或忽略。有时，当我尝试储蓄时，也会发生同样的事情；我可以选择覆盖磁盘上的更改，或放弃更改并重新加载。
怀疑网络驱动器上的分片，我将文件复制到主机的 C 驱动器并从那里共享。同样的问题。
使用我的 VM 映像（在 VM Fusion 上）在朋友的 Mac OS 10.5 上尝试过。同样的问题。
当我将文件复制到 USB 记忆棒并将其安装到虚拟机中时，不会发生这种情况。
看起来很遗憾，因为我真的很喜欢共享网络驱动器的便利，而不必担心备份、rsync 等。
你知道发生了什么吗？任何建议表示赞赏。
Spurred on by success stories of developers using VMs I've decided to give it a try. I am running Eclipse on an Ubuntu 9.04 guest, on a WinXP host. Since my networked drive on the host is backed up twice a day, I decided to share my Eclipse workspace with the VM from the networked drive.
All seems good, except on the guest Eclipse frequently pops up warnings that the file has been modified on the file system, and I can either update the editor or ignore. Sometimes the same thing happens when I try to save; I have the option to overwrite the changes on disk, or to discard my changes and reload.
Suspecting the shard on the network drive I copied the files to the C drive of the host and shared from there. Same problem.
Tried it on a friends Mac OS 10.5 using my VM image (on VM Fusion). Same problem.
Doesn't happen when I copy the files to a USB stick and mount it in the VM.
Seems such a shame, since I really like the convenience of sharing the network drive and not having to worry about backups, rsync etc.
Any ideas what's going on ? Any advise appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
最有可能的问题是文件服务器和您的计算机的时间不完全相同。这会导致文件的时间戳与 Eclipse 预期的不同，然后它会发出错误消息。
The problem most likely is that the file server and your computer do not have the exact same time. This causes the files to have a different time stamp than expected by Eclipse, and then it complains.
假设文件本身实际上没有改变，我怀疑这是文件上的时间戳。其他编辑器是否有相同设置的类似问题？
编辑：VMware 的时间戳错误，可能相关。
Assuming the files themselves did not actually change, I suspect it's the timestamp on the files. Does any other editor have similar issues with the same setup?
Edit: Timestamp bug with VMware, possibly related.