So i'm trying to reformat my cache to the new 1MiB format that gets rid of the excessive writes.  
Here's what i did:

Dissabled dockers (dont use vm's, its off)

set all shares to Cache: Yes

When i run the mover, it doesn't move from 37%.  

 

I have the Mover Tuning app, and i even disabled it.  

 

When i look in the cache it still shows folders in there:

 

Is there something new with 6.9.0 that i'm missing?  I attached the logs from when the mover was going. 

I see in the Logs: DFTPCT LIMIT USED FOR SETTING: 85

Is this still the mover tuning app not allowing the mover to work since its not above the 85% threshold?

 

 

Edit: I set the CA Mover Tuning App to:

Only move at this threshold of used cache space: 0 %

and now its working  

mover.txt

Edited March 7, 20215 yr by danimal86

14 minutes ago, danimal86 said:

set all shares to Cache: Yes

As an aside, you most likely want appdata and domains, and system to be set to useCache: Prefer

 

Depending upon how you do things, you may also want Downloads set the same way.

1 minute ago, Squid said:

As an aside, you most likely want appdata and domains, and system to be set to useCache: Prefer

 

Depending upon how you do things, you may also want Downloads set the same way.

So i have Appdata, domains, isus and system set to prefer

downloads is set to Yes

 

I plan to put it back to that once i reformat the cache....sound about right?

Yeah. (I never read the OP 😄)  Set everything to Yes.  Stop Docker in Settings - Docker.  Run mover.  Wait for it to finish.  Re-enable and set everything back to Prefer.  Run Mover 

24 minutes ago, Squid said:

Yeah. (I never read the OP 😄)  Set everything to Yes.  Stop Docker in Settings - Docker.  Run mover.  Wait for it to finish.  Re-enable and set everything back to Prefer.  Run Mover 

I bet you guys have a response ready just by the titles   (thanks for all you guys do)

 

Freaking mover stopped at 27%, i think its the CA mover tuning app telling it to stop, i removed it.....seems to be working now.