fix: 🐛 update RENAME behavior

Author: streamich

src/nfs/v4/server/operations/node/Nfsv4OperationsNode.ts

@@ -1159,12 +1159,8 @@ export class Nfsv4OperationsNode implements Nfsv4Operations {
     const oldFull = NodePath.join(savedPathAbsolute, request.oldname);
     const newFull = NodePath.join(currentPathAbsolute, request.newname);
     if (oldFull.length < this.dir.length || newFull.length < this.dir.length) throw Nfsv4Stat.NFS4ERR_NOENT;
-    // Ensure both paths are inside the server root. If target escapes, return XDEV.
-    if (!(oldFull === this.dir || oldFull.startsWith(this.dir + NodePath.sep)))
-      return new msg.Nfsv4RenameResponse(Nfsv4Stat.NFS4ERR_XDEV);
-    if (!(newFull === this.dir || newFull.startsWith(this.dir + NodePath.sep)))
-      return new msg.Nfsv4RenameResponse(Nfsv4Stat.NFS4ERR_XDEV);
-    // Now map to absolute paths (this.absolutePath will validate existence and path)
+    if (!oldFull.startsWith(this.dir)) return new msg.Nfsv4RenameResponse(Nfsv4Stat.NFS4ERR_NOENT);
+    if (!newFull.startsWith(this.dir)) return new msg.Nfsv4RenameResponse(Nfsv4Stat.NFS4ERR_NOENT);
     let oldPath: string;
     let newPath: string;
     try {

src/nfs/v4/server/operations/node/__tests__/RENAME.spec.ts

@@ -16,7 +16,7 @@ describe('RENAME operation', () => {
     vol.writeFileSync('/export/file.txt', 'data');
     // Simulate EXDEV by calling rename with invalid target outside export
     const res = await client.compound([nfs.PUTROOTFH(), nfs.SAVEFH(), nfs.RENAME('file.txt', '../outside.txt')]);
-    expect(res.status).toBe(Nfsv4Stat.NFS4ERR_XDEV);
+    expect(res.status).toBe(Nfsv4Stat.NFS4ERR_NOENT);
     await stop();
   });
 });