npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

NPM produces a lot of WARN message when used over NFS

What I Wanted to Do

following as repository gets archived and problem still occurs

What Happened Instead

I have same issue as @jplaverdure descibed in #21163, every run of npm install --no-progress produces a lot of warnings like this…

npm WARN rollback Rolling back brace-expansion@1.1.11 failed (this is probably harmless): EBUSY: resource busy or locked, unlink '<local path>/node_modules/fsevents/node_modules/brace-expansion/.nfs000000031e4acfd900000a1f'

no matter if module is going to be upgraded or not

Reproduction Steps


Platform Info

$ npm --versions
{ npm: '6.0.1',
  ares: '1.10.1-DEV',
  cldr: '32.0',
  http_parser: '2.8.0',
  icu: '60.1',
  modules: '57',
  nghttp2: '1.25.0',
  node: '8.11.1',
  openssl: '1.0.2o',
  tz: '2017c',
  unicode: '10.0',
  uv: '1.19.1',
  v8: '6.2.414.50',
  zlib: '1.2.11' }
$ node -p process.platform

I’d be curious about whether improving graceful-fs handling of EBUSY errors (see isaacs/node-graceful-fs#127) would take care of this.

Can’t see any relation with problem is about npm running over nfs mounted filesystem on linux, it has nothing to do with windows or specific module. Earlier pre 6.x versions worked just fine on same environment.

graceful-fs is a module we use for handling a variety of painful filesystem corner cases, not just Windows-specific issues.

Triage note: It’s just warnings.

Hi, I use npm over NFS [linux client & server] & this problem is quite irritating. Is there likely to be a generic (ie, non-windows specific) fix provided within graceful-fs?
Some way I can help out troubleshoot this?
I suspect that the merge/swallow of EBUSY under windows is unrelated, so might require different solution

I would also like this fixed for other platforms. I’m seeing this from within a container on Docker for Mac when I’ve mounted the working dir as an NFS mount from the host. Not sure if the problem is with the NFS server on the macOS side, or somewhere in the Linux VM/container.

This is so true with even AWS deployed EC2 instance container

npm install on a nfs mounted folder is really giving hard time and hangs

Can we please expect a FIX at the earliest or a response

Has any one looked at this yet ?

Just a remark: supporting NFS is not easy.