File Write Operations failing on Virtualbox shared filesystem

[ig-onoffice-de]

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 Box

Vagrant.configure("2") do |config|
  config.vm.box = "bento/ubuntu-22.04"

  config.vm.synced_folder "./shared_folder", "/vagrant_data"

  config.vm.provision :shell, run: :always, inline: 'which node || snap install node --classic --channel=20'
end

the file shared_folder/create-file.js

const fs = require("fs");

const writeStream = fs.createWriteStream("empty-file.txt");
writeStream.end();

and the file shared_folder/create-and-write-file.js

const fs = require("fs");

const writeStream = fs.createWriteStream("file-with-content.txt");
writeStream.write("Hello world.");
writeStream.end();

1. Start the box using vagrant up and log in to the box
2. cd /vagrant_data
3. run node create-file.js => file empty-file.txt is created
4. run node create-and-write-file.js => file file-with-content.txt is created but does not have any content!
   error message is:

node:events:492
      throw er; // Unhandled 'error' event
      ^

Error: ENOTSUP: operation not supported on socket, write
Emitted 'error' event on WriteStream instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -95,
  code: 'ENOTSUP',
  syscall: 'write'
}

Node.js v20.10.0

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

node:events:492
      throw er; // Unhandled 'error' event
      ^

Error: ENOTSUP: operation not supported on socket, write
Emitted 'error' event on WriteStream instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -95,
  code: 'ENOTSUP',
  syscall: 'write'
}

Node.js v20.10.0

Additional information

• Our hostsystem is Windows.
• node version 19 works well, but node 18 does not

The main problem for us is, that neither npm install works.

[ig-onoffice-de]

Actually, I just found out, that there is the same problem with read operations.
shared_folder/read-file.js

const fs = require("fs");

fs.readFile("helloWorld.txt", 'utf8', (err, data)=>{
		if (err) {
			console.error(err);
			return;
		}
		console.log(data);
	}
)

running node read-file.js outputs

[Error: ENOTSUP: operation not supported on socket, read] {
  errno: -95,
  code: 'ENOTSUP',
  syscall: 'read'
}

[santigimeno]

I can confirm the issue happens when writing to a vboxsf filesystem using io_uring. Possible fix here: libuv/libuv#4268