Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

many file IO operations failed #6416

Closed
billypon opened this issue Oct 20, 2015 · 7 comments
Closed

many file IO operations failed #6416

billypon opened this issue Oct 20, 2015 · 7 comments

Comments

@billypon
Copy link

when I use vbox 4.x and old version vagrant(sorry, I forgot the version number), everything are fine.
after I update to vbox 5.0.0 and vagrant 1.7.4, many file IO operations are failed
such as "Operation not permitted", "Protocol error", "No such file or directory" when I copied or move directory

@sethvargo
Copy link
Contributor

Hi @billypon

Thank you for opening an issue, and I am sorry you are having issues with Vagrant. Unfortunately there is not enough information here to reproduce or diagnose the issue. Could you please share your complete Vagrantfile as well as the output of the vagrant command in debug mode?

@billypon
Copy link
Author

@sethvargo when I ran "vagrant up --debug > vagrant.log", I see more and more output infomation, but can't save in vagrant.log. My host os is win

@sethvargo
Copy link
Contributor

Hi @billypon

I am sorry you are having issues. What do you mean you can't save in vagrant.log? Do you get an error? Unfortunately I cannot help diagnose the issue if we do not have log output.

@billypon
Copy link
Author

@sethvargo I mean debug info only print at screen, not save in vagrant.log. So I can't show you the log.

@sethvargo
Copy link
Contributor

Hi @billypon

What shell are you using?

@billypon
Copy link
Author

@sethvargo I'm using cmd shell, command is vagrant up --debug > vagrant.log

@sethvargo
Copy link
Contributor

Hi @billypon

Unfortunately without the debug logs, we are unable to provide assistance, and this does not appear to be a widespread Vagrant issue, or else we would see many other users experiencing similar issues. As such, I suspect this is something isolated to your local environment. I'm going to ask that you completely uninstall and re-install Vagrant, and if the issue persists, please open a new issue and follow our new issue template. Thanks! 😄

@hashicorp hashicorp locked and limited conversation to collaborators Apr 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants