[SOLVED] Mover fails after BTRFS / cache rebuild

[Jomscl]

Hello, last week I experienced a read only error in the cache pool (2 * 480 GB Sata SSD). The SMART report of the disks are fine. Reading the forums, I do the backup - clean and format - restore procedure. From there, the cache starts saving files and folders.

 

The new problem is, that the mover routine does not do anything, and the cache is starting to increase in size.

Here is the mover log:

 

Apr  6 08:47:55 unraid root: mover: started
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 23: unary operator expected
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 23: unary operator expected
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 23: unary operator expected
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 23: unary operator expected
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 23: unary operator expected
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 23: unary operator expected
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 23: unary operator expected
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 23: unary operator expected
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 08:47:55 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 23: unary operator expected
Apr  6 08:47:55 unraid root: mover: finished

 

I've already checked the "YES" option in the shares config.

 

Any Ideas?

 

Thanks!

[trurl]

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread 

[JorgeB]

That's a problem with the mover tuning plugin, if you change any setting and click apply it should start to work, if it doesn't remove it or post in the existing plugin support thread.

[Jomscl]

Hi @trurl, here is the diagnostic ZIP. Hope it helps!

unraid-diagnostics-20210406-0953.zip

[trurl]

41 minutes ago, JorgeB said:

mover tuning plugin

What he said.

 

But also, your system share is on the array instead of all on cache where it belongs. It always has open files so it will keep your disks spunup, and docker / VM performance will be impacted by slower array.

 

You will have to set it to cache-prefer to get it moved to cache, and also disable Docker and VM Manager in Settings since Mover (or anything else) can't move open files.

[Jomscl]

Done what @JorgeB suggest: change mover settings and later reinstall mover tunning pluggin, but the result is the same, no moving takes place (at least in move now mode)

 

Here is the pluggin reintall log:

Apr  6 12:50:01 unraid emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove ca.mover.tuning.plg
Apr  6 12:50:01 unraid root: plugin: running: anonymous
Apr  6 12:50:21 unraid emhttpd: cmd: /usr/local/emhttp/plugins/community.applications/scripts/pluginInstall.sh install https://raw.githubusercontent.com/hugenbd/ca.mover.tuning/master/plugins/ca.mover.tuning.plg
Apr  6 12:50:21 unraid root: plugin: running: anonymous
Apr  6 12:50:21 unraid root: plugin: running: anonymous
Apr  6 12:50:21 unraid root: plugin: creating: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2021.03.17-x86_64-1.txz - downloading from URL https://raw.github.com/hugenbd/ca.mover.tuning/master/archive/ca.mover.tuning-2021.03.17-x86_64-1.txz
Apr  6 12:50:22 unraid root: plugin: checking: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2021.03.17-x86_64-1.txz - MD5
Apr  6 12:50:22 unraid root: plugin: running: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2021.03.17-x86_64-1.txz
Apr  6 12:50:22 unraid root: plugin: running: anonymous

 

Here is the move command, done subsequently:

Apr  6 12:51:03 unraid emhttpd: shcmd (11455): /usr/local/sbin/mover |& logger &
Apr  6 12:51:04 unraid root: mover: started
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 24: unary operator expected
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 24: unary operator expected
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 24: unary operator expected
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 24: unary operator expected
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 24: unary operator expected
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 24: unary operator expected
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 24: unary operator expected
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 24: unary operator expected
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: cat: /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg: No such file or directory
Apr  6 12:51:04 unraid root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 181: [: 24: unary operator expected
Apr  6 12:51:04 unraid root: mover: finished

 

Any clue about the issue here?

 

And in the subject of the system folder been located in the array, I will fix that later, becouse I have some critical VM that runs in office hours. (Yes, facepalm about perfomance....) The vdisk of the VM itself is located in a phisical drive, away of the array. (The VM is regulary backed up, away from the server) Thanks @trurl for the heads up!

 

Edited April 6, 2021 by Jomscl

[trurl]

Unclear from your reply.

 

Did you actually try it with the plugin removed?

[Jomscl]

@trurl, no my mistake. I will do that first. Thanks!

 

[Jomscl]

Well, thanks @trurl and @JorgeB, The mover works just fine with the plugin unistalled. Any idea why?

 

Thanks a lot!

[trurl]

5 hours ago, JorgeB said:

post in the existing plugin support thread.

You can go directly to the correct support thread for any of your plugins by clicking on its Support Link on the Plugins page in the webUI.