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

cp command fails for filesize > 32768 bytes #21

Open
zentheme opened this issue Jul 27, 2018 · 0 comments
Open

cp command fails for filesize > 32768 bytes #21

zentheme opened this issue Jul 27, 2018 · 0 comments

Comments

@zentheme
Copy link

Hi all,

I recently upgraded to the new PRO box (v1.5) and SSH'd into the machine. Once in, I discovered that I can only copy files smaller than 32768 bytes (obviously an important number!) - anything larger throws a cp: failed to close 'myfilename.md': Input/output error error.

This if a real pain of course since build scripts can't output files and resource managers like yarn can't create node_modules dirs if they contain files larger than this.

I reverted back to the v1.0 box and everything is working fine once again.

Environment Notes:
Host Machine: Windows 10
Vagrant Version: 2.0.1_x86_64
Virtualbox Version: 5.1.30 r118389
Vagrant plugins: winNFSd (with binary installed on Windows)

Also have symlinks active on Host machine to get around "--no-bin-links" with yarn. The combo of winNFSd and symlinks works great and gives no issues at all on the older PRO version.

Anyway, pretty odd issue and just thought I'd put it out there here incase anybody has encountered it before or the specific 32768 filesize rang any bells!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant