unRAID 6.9.2 Cache @ 70%

[r00nilwazlib]

see attached photo and you will see that my 1tb cache drive is fairly full. also see screenshot of shares.I have disabled docker and vm and ran the mover twice. I am not sure if this is how it should be or not. I am still relatively new to this.

1 - is this something that needs to be addressed?

2 - can you point me to a search term or resource that will better help me understand what I need to do to fix this? 

[trurl]

attach diagnostics to your NEXT post in this thread

[r00nilwazlib]

here it is. thank you!

lockelamora-diagnostics-20220615-0922.zip

[JorgeB]

Last screenshot shows all shares set to cache=no or cache=prefer, for the mover to move data from a pool to the array you need to set the shares to cache=yes, see GUI help for more info on every option.

[r00nilwazlib]

just for the ones set to prefer?

[trurl]

4 minutes ago, JorgeB said:

all shares set to cache=no or cache=prefer

Those set to prefer are exactly the shares that should be prefer.

 

Go back to that screen, click the Compute All button at the bottom, wait for the results, and post a screenshot.

[JorgeB]

The ones that have data on cache that you want to move to the array, system shares are usually preferred on cache, so cache=prefer is OK, but it depends on what you want to do.

[trurl]

Mover ignores cache-no and cache-only shares.

 

You have shares d-------s, g---s, J---------e, m---a, T---------------p with files on cache, set those to cache-yes so mover will move them to the array.

 

Your appdata share has files on the array. You want that all on cache so docker/VMs will perform better. Nothing can move open files, so you will have to disable Docker in Settings so those can be moved.

 

But better if you temporarily set appdata to cache-only so mover will ignore it for now until you make space on cache.

[r00nilwazlib]

[r00nilwazlib]

11 minutes ago, trurl said:

Mover ignores cache-no and cache-only shares.

 

You have shares d-------s, g---s, J---------e, m---a, T---------------p with files on cache, set those to cache-yes so mover will move them to the array.

 

Your appdata share has files on the array. You want that all on cache so docker/VMs will perform better. Nothing can move open files, so you will have to disable Docker in Settings so those can be moved.

 

But better if you temporarily set appdata to cache-only so mover will ignore it for now until you make space on cache.

 

ok - I did all this and mover is running. will report back

[r00nilwazlib]

updated share config as well as dashboard. I disabled docker, ran mover, then enabled it.

[trurl]

post new diagnostics

[r00nilwazlib]

thanks for all this help. this is all new to me, but its all coming together.

lockelamora-diagnostics-20220615-1000.zip

[trurl]

d-------s still has files on cache, maybe they are duplicates or maybe mover just hasn't finished moving them.

 

g---s, m---a have files on cache. Since they are still cache-no mover won't move them.

 

33 minutes ago, trurl said:

appdata share has files on the array. You want that all on cache so docker/VMs will perform better

and also so array disks can spin down since these files are always open. appdata can be dealt with after the others are moved.

[r00nilwazlib]

I think what I have to do in the meantime is watch a sp1 video on cache drives. I am really confused.

[r00nilwazlib]

deeper explanation from my perspective of the solution for people who make this same mistake:

I had the cache settings for each share totally messed up. after the advice here, and space invader one's video on shares/cache pools, I set all of the problematic drives to settings that will allow the mover to move them, then disabled vm and docker, then used the mover. 

 

after that, I will be returning games, J drive, media, and time machine backup to NO Cache

I am fairly certain this is close to correct, but if my next steps (after the. mover is done) are wrong, let me know. otherwise thanks!!!!!

[trurl]

4 hours ago, trurl said:

Your appdata share has files on the array. You want that all on cache so docker/VMs will perform better

4 hours ago, trurl said:

and also so array disks can spin down since these files are always open. appdata can be dealt with after the others are moved.

4 hours ago, trurl said:

better if you temporarily set appdata to cache-only so mover will ignore it for now until you make space on cache.

I suggested setting appdata cache-only so mover would ignore it while you made room on cache by moving the others off cache. After that then you would set it to cache-prefer to get it all moved to cache.

 

But you have set it to cache-yes, which will get it all moved to the array. It might take a long time to move appdata to the array as you are doing now, and then another long time to get it moved to cache where it belongs.

 

1 hour ago, r00nilwazlib said:

(after the. mover is done)

When mover completes, do the Compute All screenshot and post it, along with new diagnostics.