7 hours ago, Gursh said:

Because it's not in the user path is that why this is happening? looks like there is only one file, which is how the hard links should work.

Do you think having another cache as I do, "downloadcache" might cause this?

in short, hardlinked files are not considered in my logic inside the plugin, so i sadly i have to say this doesnt work, your cache (downloadcache) setup is looking fine from user Share setup point of view, but this would end in copy file to cache, change hardlink, when done change hardlink back or whatever, so sorry, cant help here.

No worries, thanks for all the help. To clarify, hardlink is just marketing a copy of the file linked to the original since it is seeding, the only way this works is to have a separate copy in the library folder and it should work? So in sonar I should change from Hardlink to move?

23 hours ago, Gursh said:

To clarify, hardlink is just marketing a copy of the file linked to the original since it is seeding, the only way this works is to have a separate copy in the library folder and it should work? So in sonar I should change from Hardlink to move

i would say yes, and i know what hardlinks are ;)

you can easy test yourself, move some file/s to your location (after removing the hardlinks) and test.

so the real file is somewhere on

/mnt/disk1,2,3,.../media/library/movies/moviename/movie.mkv

/mnt/disk1,2,3,.../media/library/tv/showname/season N/episode.mkv

and your Share Setup is like mentioned above, so the file gets copied to

/mnt/downloadcache/media/library/movies/moviename/movie.mkv

/mnt/downloadcache/media/library/tv/showname/season N/episode.mkv

and your user Share Media is like

primary > downloadcache

secondary > array disks

and your jelly setup is like /mnt/user/media ... then yes, thats the normal setup as it should be.

Is there a guide on how to apply the settings for cache mover?

On 4/7/2026 at 6:33 PM, Hypnosis4u2nv said:

Is there a guide on how to apply the settings for cache mover?

should be self explaining ;)

also, there is a help on each function (mouse over "?"), may i ask what is unclear ?

On 3/25/2026 at 5:20 AM, alturismo said:

i would say yes, and i know what hardlinks are ;)

you can easy test yourself, move some file/s to your location (after removing the hardlinks) and test.

so the real file is somewhere on

/mnt/disk1,2,3,.../media/library/movies/moviename/movie.mkv

/mnt/disk1,2,3,.../media/library/tv/showname/season N/episode.mkv

and your Share Setup is like mentioned above, so the file gets copied to

/mnt/downloadcache/media/library/movies/moviename/movie.mkv

/mnt/downloadcache/media/library/tv/showname/season N/episode.mkv

and your user Share Media is like

primary > downloadcache

secondary > array disks

and your jelly setup is like /mnt/user/media ... then yes, thats the normal setup as it should be.

Hey, so after sometime I figured it out. I used the unbalanced app to move files which was causing these issues, not sure how the app did it. After I let the mover do its thing then tried this again it worked.


Apr 27 22:01:31 Tower root: cache-mover: msm: Number of created files: 13 (reg: 13)

Apr 27 22:01:31 Tower root: cache-mover: msm: Number of deleted files: 0

Apr 27 22:01:31 Tower root: cache-mover: msm: Number of regular files transferred: 13

Apr 27 22:01:31 Tower root: cache-mover: msm: Total file size: 28.53G bytes

Apr 27 22:01:31 Tower root: cache-mover: msm: Total transferred file size: 28.53G bytes

Apr 27 22:01:31 Tower root: cache-mover: msm: Literal data: 28.53G bytes

Apr 27 22:01:31 Tower root: cache-mover: msm: Matched data: 0 bytes

Apr 27 22:01:31 Tower root: cache-mover: msm: File list size: 0

Apr 27 22:01:31 Tower root: cache-mover: msm: File list generation time: 0.001 seconds

Apr 27 22:01:31 Tower root: cache-mover: msm: File list transfer time: 0.000 seconds

Apr 27 22:01:31 Tower root: cache-mover: msm: Total bytes sent: 28.53G

Apr 27 22:01:31 Tower root: cache-mover: msm: Total bytes received: 266

Apr 27 22:01:31 Tower root: cache-mover: msm:

Apr 27 22:01:31 Tower root: cache-mover: msm: sent 28.53G bytes received 266 bytes 193.45M bytes/sec

Apr 27 22:01:31 Tower root: cache-mover: msm: total size is 28.53G speedup is 1.00

Apr 27 22:01:31 Tower root: cache-mover: msm: open file The.Comeback.S01E01.REPACK.1080p.WEB.h264-BETTY.mkv will be switched downloadcache now

Apr 27 22:01:32 Tower root: cache-mover: msm: /mnt/downloadcache/media/library/tv/The Comeback/The.Comeback.S01E01.REPACK.1080p.WEB.h264-BETTY.mkv

Apr 27 22:01:32 Tower root: cache-mover: msm: ready to switch live

Apr 27 22:01:32 Tower root: cache-mover: msm: -: No such file or directory.

Apr 27 22:01:32 Tower root: cache-mover: msm: (gdb) Attaching to process 14506

Apr 27 22:01:32 Tower root: cache-mover: msm: [New LWP 49094]

Apr 27 22:01:32 Tower root: cache-mover: msm: [New LWP 21369]

Apr 27 22:01:32 Tower root: cache-mover: msm: [New LWP 18849]

Apr 27 22:01:32 Tower root: cache-mover: msm: [New LWP 18790]

Apr 27 22:01:32 Tower root: cache-mover: msm: [New LWP 18752]

Apr 27 22:01:32 Tower root: cache-mover: msm: [New LWP 17032]

Apr 27 22:01:32 Tower root: cache-mover: msm: [New LWP 16566]

Apr 27 22:01:32 Tower root: cache-mover: msm: [New LWP 14546]

Apr 27 22:01:32 Tower root: cache-mover: msm: [New LWP 14508]

Apr 27 22:01:32 Tower root: cache-mover: msm: [New LWP 14507]

Apr 27 22:01:32 Tower root: cache-mover: msm: [Thread debugging using libthread_db enabled]

Apr 27 22:01:32 Tower root: cache-mover: msm: Using host libthread_db library "/lib64/libthread_db.so.1".

Apr 27 22:01:32 Tower root: cache-mover: msm: 0x000014da515573ae in __syscall_cancel_arch () from /lib64/libc.so.6

Apr 27 22:01:32 Tower root: cache-mover: msm: (gdb) $1 = 257

Apr 27 22:01:32 Tower root: cache-mover: msm: (gdb) $2 = 1143

Apr 27 22:01:32 Tower root: cache-mover: msm: (gdb) $3 = 0

Apr 27 22:01:32 Tower root: cache-mover: msm: (gdb) Detaching from program: /usr/libexec/unraid/shfs, process 14506

Apr 27 22:01:32 Tower root: cache-mover: msm: [Inferior 1 (process 14506) detached]

Apr 27 22:02:04 Tower root: cache-mover: msm: update access time: /mnt/downloadcache/media/library/tv/The Comeback

@alturismo Hi there,

I still see sometimes folder permissions are reset back to "root" instead of nobody by the Cache Mover plugin. What cause sometimes issues with writing new files to directories for sonarr and radarr. Is it maybe possible to include a option to force the permission always to be set for nobody as owner with read & write permissions?

Hello,

I've been running into an issue for the past month related to using Cache Mover with Jellyfin. Before, Cache Mover was correctly able to detect media being played by Jellyfin and moved it to cache. Now, it appears Cache Mover can no longer detect media being played by Jellyfin. When I noticed it around a month ago, I tried rebooting my server and uninstalling and reinstalling Cache Mover with the same settings, neither of which fixed the issue. This also removed the old logs generated by Cache Mover so I can't reference what was logged when everything was working. Since then, the Cache Mover Logs and Cache Mover Lists tabs don't list any logs.

I also created a new Jellyfin API key and loaded that into Cache Mover, but still no fix.

I use the jellyfin:latest tag for updates (currently on 12.2), and from what I can tell 12.0 was released around the time Cache Mover stopped working for me. Are there any known changes to Jellyfin that would alter how Cache Mover connects to it?

9 hours ago, PrlthEtLBRegu3raToS- said:

I use the jellyfin:latest tag for updates (currently on 12.2), and from what I can tell 12.0 was released around the time Cache Mover stopped working for me. Are there any known changes to Jellyfin that would alter how Cache Mover connects to it?

yes, i need to change the API lookup as jelly changed it.

as im no jelly user i didnt recognize it.

as im still on a complete rewrite here, but nevertheless, i ll make a small update with
jelly12 support
uid/gid chmod after copy as some users may have issues afterwards.

Nov  1 21:00:01 PHENOM root: cache-cleaner: /usr/local/emhttp/plugins/cache-mover/scripts/cache_mover3: line 50: [: too many arguments


AI looked at the error and the script and found this fix, I've edited the script myself and testing it now.

When the script tries to evaluate a line like if [ -d $folder ]; then or if [ -d $targetdir/ ]; then using a path like /mnt/cache/My Media, the variable expands without quotes. Bash reads this as [ -d /mnt/cache/My Media ]. It interprets the space as a delimiter, thinks "Media" is an unexpected extra command argument, and throws the too many arguments error. The correct syntax in the script should be [ -d "$folder" ].

Locate the unquoted variables inside single brackets [ ] and wrap them in double quotes. Based on the snippet you provided, you need to change:

• if [ -d $folder ]; then ➔ if [ -d "$folder" ]; then

• if [ -z $targetdir ];then ➔ if [ -z "$targetdir" ]; then

• if [ -d $targetdir/ ]; then ➔ if [ -d "$targetdir/" ]; then