mirror of
https://github.com/Radarr/Radarr.git
synced 2026-03-02 22:57:34 -05:00
Changing movie's root folder fails to move (hardlink+delete) due to Cross-device link and does not fallback to copy+delete #5276
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Extras
Area: Import Lists
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Organizer
Area: Parser
Area: Scanning
Area: Tooling
Area: UI
Area: Unit Tests
On Hold: MetadataAPI Blocking
On Hold: MetadataAPI Blocking
Priority: High
Priority: Low
Priority: Medium
Status: Accepted
Status: Cannot Reproduce
Status: Confirmed
Status: Help Wanted
Status: In Progress
Status: Indexer - need invite
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: On Hold
Status: Ready for Review
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
conflict
lidarr-pull
no-conflict
not-pulled
readarr-pull
readarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Radarr#5276
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SugarDroid on GitHub (Dec 13, 2020).
Describe the bug
Changing movie's root folder is unable to move the files between drives in mergerfs pool. If hardlink enabled in media management then nothing happens, if disabled then root gets changed in the database but the files aren't moved physically.
To Reproduce
Expected behavior
A move should be move, not hardlinking and then delete the original.
Platform Information (please complete the following information):
Trace Logs
AB#719
@bakerboy448 commented on GitHub (Dec 21, 2020):
Need to know if this is reproducible on sonarr as well
either upstream issue or something radarr (netcore?) specific
@SugarDroid commented on GitHub (Dec 22, 2020):
@bakerboy448 https://github.com/Sonarr/Sonarr/issues/4185
@stale[bot] commented on GitHub (Jan 8, 2022):
This issue has been automatically marked as stale because it has not had recent activity. Please verify that this is still an issue with the latest version of Radarr and report back. Otherwise this issue will be closed.
@bakerboy448 commented on GitHub (Mar 10, 2022):
From @madhackbt on #7126
@madhackbt commented on GitHub (Mar 10, 2022):
@bakerboy448 I am using Sonarr 3.0.7.1477 (mono 6.8.0.105 on the TrueNAS-12.0-U8) and the "Move" operation works just fine. I had seen this report, but I did not have the "mergerfs" type config, Thanks for handling this.
@christianha1111 commented on GitHub (Oct 7, 2022):
I can confirm the same thing happens on Sonarr 4.2.4.6635 if mergerfs is used.
@ac1dburnz commented on GitHub (Feb 23, 2023):
Any movement on this?
@0xdevalias commented on GitHub (Apr 5, 2023):
See also:
@Panda260 commented on GitHub (Jul 8, 2025):
any updates? kinda an important bug i think
@bakerboy448 commented on GitHub (Jul 8, 2025):
The primary development team is engaged in over five applications, including Lidarr, Prowlarr, Radarr, and Sonarr. Currently, there is approximately no active developers contributing to these projects, with none of the contributors working on them full-time. Additionally, all members involved, whether in development or support roles, are volunteers and do not receive compensation for their contributions. Each team member balances their commitments alongside full-time jobs, family responsibilities, and other personal obligations.
As a result, the list of tasks to be completed across these projects, along with the various backends and modules, is extensive, while the available time for addressing these tasks is limited.
Unfortunately a toxic community and abusive users drove away the active developer into burnout.
The community also does not appear to believe this is an "important bug" as no community member has took it upon themselves to implement a solution upstream into Sonarr and/or PR downstream. This is an issue specific to edge cases and unique niche setup with certain merge file systems / configurations.