Jump to content
Sign in to follow this  
TomAsh

[solved] Mover not working

12 posts in this topic Last Reply

Recommended Posts

Posted (edited)

Well, I finally got it working by setting use cache to Yes and invoking mover.

 

----

I've been through a lot of posts but still can't get files moved off the cache.

 

I disabled both docker and VMs. I even deleted libvirt.img and docker.img

I set all shares to not use cache. I click on mover and nothing happens.

Even empty shares stay on cache.

 

I want to clear the cache drive so that I can swap it for a bigger one.

 

Aug 31 13:52:22 Tower emhttpd: req (5): cmdStartMover=Move+now&csrf_token=****************

Aug 31 13:52:22 Tower emhttpd: shcmd (70): /usr/local/sbin/mover |& logger &

Aug 31 13:52:22 Tower root: mover: started

Aug 31 13:52:22 Tower root: mover: finished

 

Any suggestions welcome

Edited by TomAsh
Found soulution

Share this post


Link to post
3 hours ago, TomAsh said:

Well, I finally got it working by setting use cache to Yes and invoking mover.

 

----

I've been through a lot of posts but still can't get files moved off the cache.

 

Any suggestions welcome

As you seem to have discovered setting the Use Cache setting to Yes is what is required to get files to move from cache to array.

 

Turning on the help built-in to the GUI might have helped you get there quicker.     The majority of GUI settings have built-in help.

Share this post


Link to post

Yes, that is how I noticed it.

 

It is not very intuitive. I expected 'No' to mean that all content will be moved to the array.

Why is it not like that?

Share this post


Link to post

Maybe it should be phrased as "Using Cache?", so then when the answer is NO its more applicable to expect Mover to not look at Cache... Maybe provide warnings when it's set to NO and it detects files still on Cache. *shrug*

Share this post


Link to post
46 minutes ago, TomAsh said:

Yes, that is how I noticed it.

 

It is not very intuitive. I expected 'No' to mean that all content will be moved to the array.

Why is it not like that?

This is partly due to history.   When the cache drive concept was first added to Unraid the only Use Case was for acting as a staging area for files and so the Yes and No values were the only options.   With the introduction of docker and VMs more complicated Use Cases have arisen and the Prefer and Only options were added, but the Yes and No options were retained unchanged.

 

it is always worth making suggestions for improving the wording so the value chosen is more intuitive.   If it is purely a wording change in the GUI without changing the underlying functionality then there is a good chance it may happen.

Share this post


Link to post

Unraid is generally easy to use but there are plenty of caveats general PC users are not aware of.

So RTFM and watch all Spaceinvader tutorials

Share this post


Link to post

I am having this same problem of Mover not moving files off of my cache drive.

 

I have a share called isos and I have set the Use Cache Disk Option to Yes. 

 

I have then gone to the Main page and clicked  the "Move Now" button.  

 

My log shows:

 

Sep  1 23:25:48 Hoylake emhttpd: req (12): cmdStartMover=Move+now&csrf_token=****************
Sep  1 23:25:48 Hoylake emhttpd: shcmd (3322): /usr/local/sbin/mover &> /dev/null &

But the file is still there:

INDEX OF /MNT/USER/ISOS
.sagetv	<DIR>	2018-01-24 04:13	Disk 3
Windows 10	<DIR>	2017-08-28 21:44	Disk 4
chromiumos_image.img	8.75 GB	2017-08-28 12:10	Disk 3
GRMSHSxFREO_EN_DVD.iso	4.31 GB	2013-01-04 19:12	Disk 3
ubuntu-16.04.1-desktop-amd64.iso	1.51 GB	2017-01-07 09:51	Cache

Any tips on what to do to get Mover to start moving files off of my Cache disk?  Do I have to stop the array to make this happen?

Share this post


Link to post
2 hours ago, wayner said:

I am having this same problem of Mover not moving files off of my cache drive.

 

I have a share called isos and I have set the Use Cache Disk Option to Yes. 

 

I have then gone to the Main page and clicked  the "Move Now" button.  

 

My log shows:

 


Sep  1 23:25:48 Hoylake emhttpd: req (12): cmdStartMover=Move+now&csrf_token=****************
Sep  1 23:25:48 Hoylake emhttpd: shcmd (3322): /usr/local/sbin/mover &> /dev/null &

But the file is still there:


INDEX OF /MNT/USER/ISOS
.sagetv	<DIR>	2018-01-24 04:13	Disk 3
Windows 10	<DIR>	2017-08-28 21:44	Disk 4
chromiumos_image.img	8.75 GB	2017-08-28 12:10	Disk 3
GRMSHSxFREO_EN_DVD.iso	4.31 GB	2013-01-04 19:12	Disk 3
ubuntu-16.04.1-desktop-amd64.iso	1.51 GB	2017-01-07 09:51	Cache

Any tips on what to do to get Mover to start moving files off of my Cache disk?  Do I have to stop the array to make this happen?

Mover will not move any file that is open so you must not have any VM running that has the iso file in question assigned to it.   To get informed feedback you should turn on mover logging and repeat, and following that provide the system diagnostics zip file (obtained via Tools->Diagnostics) so we can see what is going on.

Share this post


Link to post
1 hour ago, TomAsh said:

Can you also explain why setting share to use cache only does not move data?

As well  as reading the help it might help if you realize that the primary use of that setting is to control where NEW files are created.   Controlling mover actions is only a secondary use.

Edited by itimpi

Share this post


Link to post

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this