Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

[Plugin] Mover Tuning

Squid
in Plugin Support

Featured Replies

This Message stays the same regardless of daily activity. 
Bug or feature? 😁

 

IMG_1035.jpeg

  • Quote
    • Replies 3.5k
    • Views 485.7k
    • Created
    • Last Reply

    Top Posters In This Topic

    Popular Days

    Most Popular Posts

    • hugenbdd
      hugenbdd

      New Version 07-03-2023   HUGE thanks/Shout-out to @Swarles for the help with updating code fixes and adding a great new feature.  You can now have some customization per share.  It's great t

    • hugenbdd
      hugenbdd

      How to ignore a SINGLE file 1.) Find the path of the file you wish to ignore.     ls -ltr /mnt/cache/Download/complete/test.txt         root@Tower:/# ls -ltr /mnt/cache/Download/complete/test

    • Reynald
      Reynald

      Hi all, I made a new version of the plugin. This fork replaces @hugenbdd's plugin which is not maintained anymore and will land in community applications if your feedbacks are positive.  

    Posted Images

    You're in test mode so nothing gets done. Possible it's always been that way so no last sync date since none ever happened?

  • Quote
    • Like 1
    Just now, Kilrah said:

    You're in test mode so nothing gets done. Possible it's always been that way so no last sync date since none ever happened?

    No Sir, test mode has in fact been switched on again for the first time last night. Before it was running in real mode for some days. No matter which mode it was running in the message stayed the same. 

  • Quote
    41 minutes ago, b-riched said:

    Bug or feature

    It's for the first time only

  • Quote
    35 minutes ago, b-riched said:

    No matter which mode it was running in the message stayed the same. 

    Test mode can't turn on by self, just disable it, and set scheduling of mover or run 'mover start' in cmd or by move button

  • Quote
    1 hour ago, Masterwishx said:

    Test mode can't turn on by self, just disable it, and set scheduling of mover or run 'mover start' in cmd or by move button

    Not sure whether we talk about the same thing. 
    Toggling test mode is not the issue. Mover has been running for two weeks now in either test or real mode.
    Issue is: last sync date message stays on 1970-01-01 regardless of mover running in the past in whatever mode. 
     

    Me personally couldn’t care less but if the last sync date determines the mover’s behaviour (which it presumably does) it is probably worth having a closer look? 

    IMG_1036.jpeg

    IMG_1037.jpeg

    IMG_1038.jpeg

  • Quote
    11 minutes ago, b-riched said:

    Me personally couldn’t care less but if the last sync date determines the mover’s behaviour

     

    you need to check the logs if actual synchronization was runned ,if it was then the date of last sync  needs to be saved in config file

    Edited by Masterwishx

  • Quote
    38 minutes ago, b-riched said:

    Me personally couldn’t care less but if the la

     

    Did you modified files on cache ?

     

    image.thumb.png.7303e6357915f765e19daa581806e394.png

  • Quote
    17 minutes ago, Masterwishx said:

     

    Did you modified files on cache ?

     

    image.thumb.png.7303e6357915f765e19daa581806e394.png

    Yes, I did, and the mover was counting them all for actions. 
    specifically, I touched some 1500 files reading from the array which were not stored in the cache. I created 201 files which are saved to the cache and the mover identified them for syncing (but did not sync due to test mode).  

  • Quote
    1 hour ago, Masterwishx said:

     

    you need to check the logs if actual synchronization was runned ,if it was then the date of last sync  needs to be saved in config file

    Hmmmm

    /config/plugins/ca.mover.tuning/ca.mover.tuning.cfg

    tells me: version="2025.05.04"

    although I thought it had updated recently. 
    Cannot find any last update date in here. 
     

    Anyway, log of 2025-05-16 tells me mover was on sync, no test, synced 3 files to array. Last sync day was not updated (at least not in the log file). 

  • Quote
    3 minutes ago, b-riched said:

    Last sync day was not updated (at least not in the log file). 

    Check config file last sync date should be saved there. 

  • Quote
    7 minutes ago, Masterwishx said:

    Check config file last sync date should be saved there. 

    I am afraid it isn’t. If I am looking at the right file. 

    === /config/plugins/ca.mover.tuning/ca.mover.tuning.cfg ===

    testmode="no"
    logging="yes"
    movenow="yes"
    version="2025.05.04"
    freeingThreshold="70"
    fillupThreshold="0"
    omovercfg="no"
    age="yes"
    cleanFolders="yes"
    cleanDatasets="no"
    ctime="no"
    atime="no"
    enableTurbo="no"
    filelistf="no"
    filetypesf="no"
    ignoreHidden="no"
    rebalanceShares="no"
    sizef="no"
    sparsnessf="no"
    synchronizeCache="yes"
    resynchronizeCache="no"
    notify="yes"
    debuglogging="no"
    loggingFolder="/tmp"
    logfilesDaysold="5"
    listfilesDaysold="10"
    validateFilenames="yes"
    moverDisabled="no"
    advancedSettings="no"
    parity="yes"
    moverNice="0"
    moverIO="-c 2 -n 0"
    force="no"
    beforeScript=""
    afterScript=""
    movingThreshold="90"
    advancedFilters="yes"
    advancedOptions="no"
    daysold="-1"
    === 

     

  • Quote
    4 minutes ago, b-riched said:

    I am afraid it isn’t. If I am looking at the right file. 

    === /config/plugins/ca.mover.tuning/ca.mover.tuning.cfg ===

    testmode="no"
    logging="yes"
    movenow="yes"
    version="2025.05.04"
    freeingThreshold="70"
    fillupThreshold="0"
    omovercfg="no"
    age="yes"
    cleanFolders="yes"
    cleanDatasets="no"
    ctime="no"
    atime="no"
    enableTurbo="no"
    filelistf="no"
    filetypesf="no"
    ignoreHidden="no"
    rebalanceShares="no"
    sizef="no"
    sparsnessf="no"
    synchronizeCache="yes"
    resynchronizeCache="no"
    notify="yes"
    debuglogging="no"
    loggingFolder="/tmp"
    logfilesDaysold="5"
    listfilesDaysold="10"
    validateFilenames="yes"
    moverDisabled="no"
    advancedSettings="no"
    parity="yes"
    moverNice="0"
    moverIO="-c 2 -n 0"
    force="no"
    beforeScript=""
    afterScript=""
    movingThreshold="90"
    advancedFilters="yes"
    advancedOptions="no"
    daysold="-1"
    === 

     

    Yep, can you modify file on cache that need to be sync and run mover again? 

  • Quote
    30 minutes ago, Masterwishx said:

    Yep, can you modify file on cache that need to be sync and run mover again? 

    Yup… 

    modified some files, reran mover.
    Log states it updated the sync day. 
    Cfg. files contains:  lastCacheSync=1747568606

     

    So seems to work although I don’t understand why it didn’t before. 
    Thx. 

  • Quote
    • Like 1
    1 minute ago, b-riched said:

    So seems to work although I don’t understand why it didn’t before. 

     

    Becouse as i told befor you need to read the help description of options :  

     

    where said : 

    `Only modified files since last sync are synchronized.`

     

    So if was no changes was no sync at all 

     

     

     

     

     

  • Quote
    17 minutes ago, Masterwishx said:

     

    Becouse as i told befor you need to read the help description of options :  

     

    where said : 

    `Only modified files since last sync are synchronized.`

     

    So if was no changes was no sync at all 

     

     

     

     

     

    Hermine to Ron and Harry: “Honestly boys, it would do you good reading!” 😁

  • Quote
    • Like 1

    It seems that files including a $ cannot be moved? For example the file below, but also many others:

     

    Error: Invalid filename path: 'data/media/movies/$5 a Day (2008)/Trailers/$5 a Day - Trailer-trailer.mkv'. Please either change the filename to valid or disable the 'Validate input filenames' option.

  • Quote
    1 hour ago, steve1977 said:

    It seems that files including a $ cannot be moved? For example the file below, but also many others:

     

    Error: Invalid filename path: 'data/media/movies/$5 a Day (2008)/Trailers/$5 a Day - Trailer-trailer.mkv'. Please either change the filename to valid or disable the 'Validate input filenames' option.

    The file does not get moved even after disabling "validate input filenames" options. The error message disappears, but nothing is moved.

  • Quote
    37 minutes ago, steve1977 said:

    but nothing is moved.

    Check what the log says. 

    Or download debug.zip and send to me

  • Quote

    Hi.  My new mover tuning plugin does not seem to work since I upgraded to the latest version.  My cache drive filled up yesterday and I noticed the mover was not running properly.   Here is my setup and analysis so far.

     

    1. Unraid 6.12.15.
    2. I used to run the older version CA mover tuning plugin fine for years.  I noticed my version has been deprecated in CA.
    3. Uninstalled deprecated version.  
    4. Installed new version from CA.  version 2025.05.04.
    5. Left all default values for plugin.
    6. Click "Move now" and see this in the logs:

      

    May 18 18:42:53 unraid root: plugin: creating: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2025.05.04-x86_64-1.txz - downloading from URL https://github.com/masterwishx/ca.mover.tuning/raw/master/archive/ca.mover.tuning-2025.05.04-x86_64-1.txz
May 18 18:42:54 unraid root: plugin: checking: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2025.05.04-x86_64-1.txz - MD5
May 18 18:42:54 unraid root: plugin: running: upgradepkg --install-new /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2025.05.04-x86_64-1.txz
May 18 18:42:54 unraid root: plugin: running: anonymous
May 18 18:42:55 unraid root: plugin: ca.mover.tuning.plg installed
May 18 18:44:11 unraid emhttpd: shcmd (264): /usr/local/sbin/mover |& logger -t move &
May 18 18:44:11 unraid move: Starting Mover ...
May 18 18:44:11 unraid move: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover 
May 18 18:44:11 unraid move: Mover Tuning Plugin version 2025.05.04
May 18 18:44:11 unraid move: 
May 18 18:44:11 unraid move: Usage: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start [-e <disk_name>]
May 18 18:44:11 unraid move:        /usr/local/emhttp/plugins/ca.mover.tuning/age_mover stop|softstop|status|reset
May 18 18:44:11 unraid move:        <disk_name> must match pattern 'disk[0-9]*'
May 18 18:44:11 unraid move: 
May 18 18:44:11 unraid move: reset  - reset config file to default values and delete override config folder


    It just doesn't seem to run the mover.     Why is the "Usage" error showing up in the logs?

     

    What should I check for, or am I missing something?

     

    Thanks!!!  -Glenner.

  • Quote
    2 hours ago, glenner said:

    Hi.  My new mover tuning plugin does not seem to work since I upgraded to the latest version.  My cache drive filled up yesterday and I noticed the mover was not running properly.   Here is my setup and analysis so far.

     

    1. Unraid 6.12.15.
    2. I used to run the older version CA mover tuning plugin fine for years.  I noticed my version has been deprecated in CA.
    3. Uninstalled deprecated version.  
    4. Installed new version from CA.  version 2025.05.04.
    5. Left all default values for plugin.
    6. Click "Move now" and see this in the logs:

      

    May 18 18:42:53 unraid root: plugin: creating: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2025.05.04-x86_64-1.txz - downloading from URL https://github.com/masterwishx/ca.mover.tuning/raw/master/archive/ca.mover.tuning-2025.05.04-x86_64-1.txz
May 18 18:42:54 unraid root: plugin: checking: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2025.05.04-x86_64-1.txz - MD5
May 18 18:42:54 unraid root: plugin: running: upgradepkg --install-new /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2025.05.04-x86_64-1.txz
May 18 18:42:54 unraid root: plugin: running: anonymous
May 18 18:42:55 unraid root: plugin: ca.mover.tuning.plg installed
May 18 18:44:11 unraid emhttpd: shcmd (264): /usr/local/sbin/mover |& logger -t move &
May 18 18:44:11 unraid move: Starting Mover ...
May 18 18:44:11 unraid move: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover 
May 18 18:44:11 unraid move: Mover Tuning Plugin version 2025.05.04
May 18 18:44:11 unraid move: 
May 18 18:44:11 unraid move: Usage: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start [-e <disk_name>]
May 18 18:44:11 unraid move:        /usr/local/emhttp/plugins/ca.mover.tuning/age_mover stop|softstop|status|reset
May 18 18:44:11 unraid move:        <disk_name> must match pattern 'disk[0-9]*'
May 18 18:44:11 unraid move: 
May 18 18:44:11 unraid move: reset  - reset config file to default values and delete override config folder


    It just doesn't seem to run the mover.     Why is the "Usage" error showing up in the logs?

     

    What should I check for, or am I missing something?

     

    Thanks!!!  -Glenner.

     

    I'm on the same Unraid version and have the same error. I fixed it by uninstalling the current plugin and installing "2025.04.05" version of the plugin. Might need to disable auto update after. Woke up this morning and noticed Mover Tuning got updated again to the latest.

  • Quote
    Quote

    I'm on the same Unraid version and have the same error. I fixed it by uninstalling the current plugin and installing "2025.04.05" version of the plugin. Might need to disable auto update after. Woke up this morning and noticed Mover Tuning got updated again to the latest.

    How do I install a backlevel version of the plugin?  I've never done that.  I only seem to be able to uninstall and reinstall the current version.  Thanks!

     

     

  • Quote
    12 hours ago, Masterwishx said:

    Check what the log says. 

    Or download debug.zip and send to me

    The Unraid log says that it completed successfully and the files were moved. However, the files remain on the cache drive and are not moved (though it says so).

     

    Where can I find the debug.zip? I am not so good with command line.

  • Quote
    6 minutes ago, steve1977 said:

    Where can I find the debug.zip? I am not so good with command line.

    In plugin help menu

  • Quote
    5 hours ago, glenner said:

    Unraid 6.12.15.

    I made a fix for this version can you check it befor release? 

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.