Skip to content

Tdarr 2.50.01: EPERM copyfile errors on SMB mounts due to Ubuntu 24.04 kernel changes #1275

@Apocrathia

Description

@Apocrathia

Describe the bug
Tdarr 2.50.01 fails to copy files from SMB source mounts to SMB scratch mounts with EPERM: operation not permitted, copyfile errors. This occurs when transcoding files, preventing any transcoding operations from completing.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy Tdarr 2.50.01 with SMB-mounted source directories and SMB-mounted scratch directory
  2. Configure transcoding flows to process files
  3. Attempt to transcode any media file
  4. Observe EPERM: operation not permitted, copyfile errors in node logs

Expected behavior
Tdarr should successfully copy source files to the scratch directory for transcoding operations, as it did in previous versions.

Screenshots
N/A - Error logs provided below

Please provide the following information:

  • Config files: Using Kubernetes deployment with SMB CSI driver mounts
  • Job reports: All jobs fail with copyfile errors
  • Log files:
[2025-10-23T12:02:40.774] [ERROR] Tdarr_Node - Error: EPERM: operation not permitted, copyfile '/source/[...]/file.mkv' -> '/scratch/[...]/file.mkv'
    at async Object.copyFile (node:internal/fs/promises:623:10){
  "errno": -1,
  "code": "EPERM",
  "syscall": "copyfile",
  "path": "/source/[...]/file.mkv",
  "dest": "/scratch/[...]/file.mkv"
}
  • Worker error: Same as above - copyfile syscall fails with EPERM
  • OS: Linux (Kubernetes/Talos)
  • Browser: N/A
  • Version: 2.50.01

Additional context
This issue appears to be related to Tdarr 2.50.01's update from Ubuntu 22.04 (Jammy) to Ubuntu 24.04 (Noble) base image. Ubuntu 24.04's kernel (6.8+) has stricter requirements for the copy_file_range() syscall used by Node.js's fs.copyFile() when operating across different mount points, particularly SMB/CIFS mounts.

The issue does not occur in Tdarr 2.49.01 with Ubuntu 22.04 base image. All SMB mounts are properly configured with correct permissions and work fine for other operations,

Workaround: Downgrading to Tdarr 2.49.01 resolves the issue immediately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions