-
Notifications
You must be signed in to change notification settings - Fork 29k
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
File Write Operations failing on Virtualbox shared filesystem #50876
Labels
confirmed-bug
Issues with confirmed bugs.
fs
Issues and PRs related to the fs subsystem / file system.
libuv
Issues and PRs related to the libuv dependency or the uv binding.
Comments
Actually, I just found out, that there is the same problem with read operations. const fs = require("fs");
fs.readFile("helloWorld.txt", 'utf8', (err, data)=>{
if (err) {
console.error(err);
return;
}
console.log(data);
}
) running
|
santigimeno
added a commit
to santigimeno/libuv
that referenced
this issue
Dec 28, 2023
Fallback to the threadpool if it returns `EOPNOTSUPP`. Fixes: nodejs/node#50876
I can confirm the issue happens when writing to a |
santigimeno
added a commit
to santigimeno/libuv
that referenced
this issue
Jan 4, 2024
Fallback to the threadpool if it returns `EOPNOTSUPP`. Fixes: nodejs/node#50876
santigimeno
added a commit
to libuv/libuv
that referenced
this issue
Jan 8, 2024
Fallback to the threadpool if it returns `EOPNOTSUPP`. Fixes: nodejs/node#50876
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
confirmed-bug
Issues with confirmed bugs.
fs
Issues and PRs related to the fs subsystem / file system.
libuv
Issues and PRs related to the libuv dependency or the uv binding.
Version
20.10.0
Platform
Linux vagrant 5.15.0-83-generic #92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
I have the following
Vagrantfile
to set up my Virtual Boxthe file
shared_folder/create-file.js
and the file
shared_folder/create-and-write-file.js
vagrant up
and log in to the boxcd /vagrant_data
node create-file.js
=> fileempty-file.txt
is creatednode create-and-write-file.js
=> filefile-with-content.txt
is created but does not have any content!error message is:
How often does it reproduce? Is there a required condition?
It always happens with the shared filesystem
What is the expected behavior? Why is that the expected behavior?
File should have content.
What do you see instead?
This error message and an empty file
Additional information
The main problem for us is, that neither
npm install
works.The text was updated successfully, but these errors were encountered: