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.
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!
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 errorerror.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!