1 minute ago, GoChris said:

From a cache device to the array.

The only reason for a cache : no share to have files on the cache is something misconfigured, or have files placed there on purpose that shouldn't be moved.

10 minutes ago, jonathanm said:

The only reason for a cache : no share to have files on the cache is something misconfigured, or have files placed there on purpose that shouldn't be moved.

It's also possible that a share got changed from yes to no without mover running.  Leaving them orphaned.  

 

I don't think its best to be built into the plug-in.  Probably better to use something like Midnight Commander.  

 

However, I can still be convinced to look into it for a good reason.

8 minutes ago, jonathanm said:

The only reason for a cache : no share to have files on the cache is something misconfigured, or have files placed there on purpose that shouldn't be moved.

Perhaps in your setup sure, but I don't consider it a misconfiguration. I have large files that when created or downloaded need/benefit from my speedy cache device. But if files are copied to the share from other devices on the network, there is no reason to use the cache device (as they are quite large) so prefer them to go straight to the array. These files are created on the cache, then they get moved to the share folder, which, won't move them to the array the way it works, and then the mover also won't pick them up.

I could exploit the bug (IMO) that the min free space required for a share also applies to the cache device as well, and set that value to be larger than the cache size (that only works while you have large enough free space on some data drives).

2 minutes ago, hugenbdd said:

It's also possible that a share got changed from yes to no without mover running.  Leaving them orphaned.  

 

I don't think its best to be built into the plug-in.  Probably better to use something like Midnight Commander.  

 

However, I can still be convinced to look into it for a good reason.

Also this too, that can happen.

Apologies if this has already been covered in this thread but I was struggling with what to search for.

 

Is there a way to prioritize a share so that Mover acts on it more frequently than the default Mover settings? My situation is that I have the settings to generally not have the Mover run unless the cache is running low on disk space. But, I have Nextcloud uploads going to cache and I'd like those to get moved to the array a bit more often than all the other stuff on the cache.

Not from my plug-in.

 

If you have a lot of experience you can create your own command line and pipe the output to the mover binary.  

 

Something like below in a cron entry. (User scripts plug-in).  However... you won't have any of the supporting code around it.  i.e. to see if mover is currently running.

 

find "/mnt/cache/<YOURSHAREHERE>" -depth | /usr/local/sbin/move -d 1

 

 

 

 

21 hours ago, hugenbdd said:

Not from my plug-in.

 

If you have a lot of experience you can create your own command line and pipe the output to the mover binary.  

 

Something like below in a cron entry. (User scripts plug-in).  However... you won't have any of the supporting code around it.  i.e. to see if mover is currently running.

 

find "/mnt/cache/<YOURSHAREHERE>" -depth | /usr/local/sbin/move -d 1

 

Ah, no worries. Probably a bit outside my technical abilities at this stage. Thanks!

Edited August 26, 20214 yr by mudsloth

Hmm, will we need an updated plugin for 6.10? It appears to not apply the tuning settings and just uses Unraid's default mover.

Possibly.  I don't have 6.10 yet.  I'm still on 6.9.1

I'll update my dev box this week.

 

What might have happened is that 6.10 provided a new mover script.  Overwritting the plug-in's script which just points to the plug-in's new script or the original script.  You might be able to get the plug-in working by removing then re-installing the plug-in.

 

33 minutes ago, hugenbdd said:

Possibly.  I don't have 6.10 yet.  I'm still on 6.9.1

I'll update my dev box this week.

 

What might have happened is that 6.10 provided a new mover script.  Overwritting the plug-in's script which just points to the plug-in's new script or the original script.  You might be able to get the plug-in working by removing then re-installing the plug-in.

 

Ahh, I see! No luck on removing / re-adding. Didn't try a reboot between those two, however.

36 minutes ago, hugenbdd said:

What might have happened is that 6.10 provided a new mover script.  Overwritting the plug-in's script which just points to the plug-in's new script or the original script.  You might be able to get the plug-in working by removing then re-installing the plug-in.

Unraid update would have required a reboot. In fact, the new version isn't loaded until the next boot.

 

After the new version loads, the built-in mover script is in RAM just like the rest of the OS.

 

Then any installed plugins are applied.

1 hour ago, hugenbdd said:

Possibly.  I don't have 6.10 yet.  I'm still on 6.9.1

I'll update my dev box this week.

 

What might have happened is that 6.10 provided a new mover script.  Overwritting the plug-in's script which just points to the plug-in's new script or the original script.  You might be able to get the plug-in working by removing then re-installing the plug-in.

 

not sure if this helps but, I verified /usr/local/sbin/mover is the plugin and mover.old is the original. calling mover by itself doesn't work as intended but running /usr/local/emhttp/plugins/ca.mover.tuning/mover.php with the parameters I want does. not sure where the disconnect is happening.

28 minutes ago, classiccrime said:

not sure if this helps but, I verified /usr/local/sbin/mover is the plugin and mover.old is the original. calling mover by itself doesn't work as intended but running /usr/local/emhttp/plugins/ca.mover.tuning/mover.php with the parameters I want does. not sure where the disconnect is happening.

Is it the button in the scheduler page that isn't working or when it is run at it's scheduled time?

 

(Sorry, will play around with tonight/tomorrow)

50 minutes ago, classiccrime said:

not sure if this helps but, I verified /usr/local/sbin/mover is the plugin and mover.old is the original. calling mover by itself doesn't work as intended but running /usr/local/emhttp/plugins/ca.mover.tuning/mover.php with the parameters I want does. not sure where the disconnect is happening.

Forgot.. (I have to many options in the plugin....)

 

But do you have this set? (Second to last question)

Move Now button follows plug-in filters: Yes

5 minutes ago, hugenbdd said:

Forgot.. (I have to many options in the plugin....)

 

But do you have this set? (Second to last question)

Move Now button follows plug-in filters: Yes

Oh my goodness! My apologies. That was it. Is that a new-ish option?

4 minutes ago, classiccrime said:

Oh my goodness! My apologies. That was it. Is that a new-ish option?

Newer...

Previously I had a separate button, but Squid gave me direction in how to add this back in so I added it as an option.

Just now, hugenbdd said:

Newer...

Previously I had a separate button, but Squid gave me direction in how to add this back in so I added it as an option.

Understood, thank you for the help! I was running an older plugin version then updated it when I went to 6.10

Ok Guys/Girls

 

i can't figure out why my mover isn't working.

i want to keep my ssd as empty as i can 

 

can you help with settings to make it move everything hourly?

and keep my ssd drive 25% full?

 

Edited September 20, 20214 yr by Vader666

Try setting this to 0 and not 1.

Move files that are greater than this many days old:

 

You can also run in test mode and review the files it will be selecting.  (see the log file)

20 minutes ago, hugenbdd said:

Try setting this to 0 and not 1.

Move files that are greater than this many days old:

 

You can also run in test mode and review the files it will be selecting.  (see the log file)

 OK i just changed that setting and hit start so i will see what happens

thank you 

26 minutes ago, hugenbdd said:

Try setting this to 0 and not 1.

Move files that are greater than this many days old:

 

You can also run in test mode and review the files it will be selecting.  (see the log file)

  so it gets to 60gig free space and stops moving 

 

Just now, Vader666 said:

  so it gets to 60gig free space and stops moving 

 

 

Enable logging, then check what files are left.
 

Do you have other shares using this cache drive?  (i.e. appdata)

3 minutes ago, Vader666 said:

  so it gets to 60gig free space and stops moving 

 

And you probably want to set this to no.

 

Move files off cache based on age?

4 minutes ago, hugenbdd said:

And you probably want to set this to no.

 

Move files off cache based on age?

ok i will change that 

 

also not sure how to check the logging and what files are left.  super new to all of this 

 

 

1 minute ago, Vader666 said:

ok i will change that 

 

also not sure how to check the logging and what files are left.  super new to all of this 

 

 

 

Mover Logging : Enabled. (Up top, schedule area)

 

You can see in your last pic the "mover started.      Mover Finished". at the bottom.  That will expand to a lot more.

 

You will need to browse the individual cache drive or use the console and issue ls commands on the cache.

https://www.tecmint.com/15-basic-ls-command-examples-in-linux/

 

also

https://www.techrepublic.com/article/linux-directory-navigation-tips-and-tricks/#:~:text=To change to your home,and then press [Enter].