NFS is not responding with npm #61
Comments
|
After taking a quick look at winnfsd logs it looks like it might be problem with npm itself, which is not deleting all directory content befere trying to rmdir (and it basicaly sucks, because it spams console with "WRITE" messages on every log line). But I also noticed such Input/Output errors when just deleting large amount of files by myself. Oh, and I updated winnfsd.exe to version mentioned in #60, and for now everything looks fine, but i will try to give more feedback if needed. |
|
Win 8.1, VBOX 5, Vagrant 1.7.4, CentOS 7.1 I get errors installing packages as well.. It works fine if I use "npm some package -g" to install the package globally. Here's the output on NFS 0 info it worked if it ends with ok |
|
I got this same error. I ended up just npm installing the modules into a folder that is not being synced, then symlinking it to where I actually wanted to run the install. This was an acceptable workaround for me. Installing them globally also worked, but npm 3 does not install global modules into a flat dependency tree. |
|
@mikestaub Try doing symlink of your package.json to another directory, thats not being synced and download all packeges in that place and rsync them with your tree later on. It's not best solution but it works really well and you're not making mess on your windows drive. |
|
I'm guessing this has to do with the excessively deep structure that |
|
This should be fixed with v1.2.0. Please update and try again. |
|
Upgraded to v1.3.0 and having exact issue. Can anyone else still reproduce this result on the newer WinNFSd? In this case CentOS7 guest on a Win7 host with Vagrant 1.8.1. npm ERR! Linux 3.10.0-123.el7.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v6.7.0
npm ERR! npm v3.10.3
npm ERR! path /websites/myapp/node_modules/.staging
npm ERR! code EIO
npm ERR! errno -5
npm ERR! syscall rmdir
npm ERR! EIO: i/o error, rmdir '/websites/myapp/node_modules/.staging'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues> |
|
please see #96 for further progress on this. i just uploaded a beta version which probably fixes this issue. |
|
Should be fixed with winnfsd 2.3.1 |
|
We are still encountering same issues and only workaround so far is the same @kadet1090 describes. |
There seems to be some problem with larger operations. When I for example try to remove directory which contains many dirs and files (about 533 dirs, dependencies downloaded by npm, don't ask..) nfs is not responding and system throws I/O error. In fact I can't even install packages via npm because of that because i'm still getting such an error:
And with that comes few messages in
dmesg:I'm using windows 8.1 Pro as host, and puppetlabs/ubuntu-14.04-64-puppet as my vm in virtualbox.
The text was updated successfully, but these errors were encountered: