Skip to content
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

Synology's shared folders affect fs.rename and raise EXDEV errors #44963

Closed
LarkinZero opened this issue Oct 11, 2022 · 1 comment
Closed

Synology's shared folders affect fs.rename and raise EXDEV errors #44963

LarkinZero opened this issue Oct 11, 2022 · 1 comment
Labels
invalid Issues and PRs that are invalid.

Comments

@LarkinZero
Copy link

LarkinZero commented Oct 11, 2022

Version

v16.13.1

Platform

Linux NAS 4.4.180+ #42962 SMP Wed Sep 21 10:56:47 CST 2022 x86_64 GNU/Linux synology_apollolake_218+

Subsystem

Synology DS218+

What steps will reproduce the bug?

No response

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

rename successful

What do you see instead?

/volume2/File is a shared directory for the Synology DSM.
/volume2/File1 is created by sudo mkdir /volume2/File1.

sudo node
> fs.rename('/volume2/File/proxmox-ve_6.1-1.iso','/volume2/File1/proxmox-ve_6.1-1.iso',(err) => { if (err) throw err;  console.log('Rename complete!');})
undefined
> Uncaught:
[Error: EXDEV: cross-device link not permitted, rename '/volume2/File/proxmox-ve_6.1-1.iso' -> '/volume2/File1/proxmox-ve_6.1-1.iso'] {
  errno: -18,
  code: 'EXDEV',
  syscall: 'rename',
  path: '/volume2/File/proxmox-ve_6.1-1.iso',
  dest: '/volume2/File1/proxmox-ve_6.1-1.iso'
}

Additional information

Related issues
coderaiser/cloudcmd#384

@LarkinZero LarkinZero changed the title Synology's shared folder affects fs.rename Synology's shared folders affect fs.rename and raise EXDEV errors Oct 11, 2022
@bnoordhuis
Copy link
Member

EXDEV: cross-device link not permitted

The operating system doesn't support what you're trying to do. There's nothing node can do about that.

I'll close this as not-a-bug but I can move it to a discussion if you have follow-up questions.

@bnoordhuis bnoordhuis closed this as not planned Won't fix, can't repro, duplicate, stale Oct 11, 2022
@Trott Trott added the invalid Issues and PRs that are invalid. label Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Issues and PRs that are invalid.
Projects
None yet
Development

No branches or pull requests

3 participants