NodeJS File System fs.open UNKNOWN: unknown error

[kmocorro]

• Version: v8.11.1
• Platform: 64-bit (Windows)
• Subsystem: FS

Hi node!

Few days ago, fs.watch() was still able to work with my path ////networkFolder. But after I restarted the server (hard reset), it gave me an unknown error.

Now for me to check the path I did some troubleshooting, so I used fs.open() but it gave me an error.

fs.open('\\\\networkFolder\\sharedFolder\\p\\a\\t\\h', 'r',  (err, fd) => {
    if(err) throw err;
    fs.close(fd, (err) => {
       if (err) throw err;
    });
});

Error: UNKNOWN: unknown error, open '\\networkFolder\sharedFolder\p\a\t\h'

Then I used fs.stat() to verify:

fs.stat('\\\\networkFolder\\sharedFolder\\p\\a\\t\\h', function(err, stat){
   if(err){
      console.log(err);
   } else {
      console.log(stat);
   }
});

{ Error: UNKNOWN: unknown error, stat '\\networkFolder\sharedFolder\p\a\t\h'
  errno: -4094,
  code: 'UNKNOWN',
  syscall: 'stat',
  path: '\\\\networkFolder\\sharedFolder\\p\\a\\t\\h' }

From what I remember, I've used net use to setup my network folder but I don't know if that actually help/works in my problem. I did it again but still no luck for me

Please let me know your thoughts regarding the issue.

Thank you!

[bzoz]

Is the network share accessible in any other application?

[kmocorro]

.. accessible in any other application?

I haven't tried it to other application, since it's my only app that listen to a file.

Although I used net use and it works fine then in cmd, I tried C:> dir ////networkFolder//shareFolder no error and also already mapped the network share with and without drive letter.

Few days ago it runs smoothly. The app can listen to the file changes using fs.watch. I don't know why all of a sudden fs.watch(), .stat(), .open() seems not to work right after restarting the server.

[bnoordhuis]

That 4094 error code is a generic network-or-configuration error, Node.js just passes it on from the operating system.

Apropos fs.watch(), note the caveat from the documentation:

watching files or directories can be unreliable, and in some cases impossible, on network file
systems (NFS, SMB, etc)

I'm closing out the issue since it isn't a bug in Node.js itself. If you have follow-up questions, please post them to the nodejs/help repo. You're probably better off getting in touch with your network administrator, though.