Cache drive full overnight

[Hasodi]

Unraid 6.8 rc8

 

i just setup a 500gb cache drive. Had a few files in it that were to be moved at 3am. 
I woke up to a full cache drive. 

 

files from the array were moved to the cache...

 

any ideas?

[trurl]

Likely you set some shares to cache-prefer instead of cache-yes. Prefer means 

13 minutes ago, Hasodi said:

from the array were moved to the cache...

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post. 

[Hasodi]

I am at work connected to unraid server on my iPad.
 

I absolutely had my shares set to cache-prefer. I did not read the very last line on the difference between prefer and yes. 
 

I set all shares to yes just now and invoked the mover. The SSD is moving back to the array. 
 

Sorry for the basic question but super thank you for the quick response. 
Glad I purchased and happy holidays. 

[itimpi]

1 minute ago, Hasodi said:

I absolutely had my shares set to cache-prefer. I did not read the very last line on the difference between prefer and yes. 

Since you are on the 6.8 release the text to the right of the Use Cache setting should explain what mover will do.   Any suggestions on how this could have been improved to stop you selecting the wrong option?

[Hasodi]

When I look at the text now it is very obvious. My brain must have swapped array and cache around.
 

I woke up to multiple email alerts and was panicked. 
 

One suggestion could possibly be to bold the word array and cache. 

Edited December 12, 2019 by Hasodi

[jlficken]

1 hour ago, Hasodi said:

When I look at the text now it is very obvious. My brain must have swapped array and cache around.
 

I woke up to multiple email alerts and was panicked. 
 

One suggestion could possibly be to bold the word array and cache. 

 

I like this suggestion.  You could also change the color of the text of those words possibly.

[trurl]

2 hours ago, Hasodi said:

I set all shares to yes just now and invoked the mover.

If you have or intend to have Dockers or VMs you don't want all shares on the array either.

 

Post those diagnostics so we can make more detailed recommendations on your setup.

[Hasodi]

To clarify, I meant all custom shares were set to Yes.  Not system created shares.

 

Anything stand out?

 

 

Edited December 12, 2019 by Hasodi

[trurl]

1 minute ago, Hasodi said:

To clarify, I meant all custom shares were set to Yes.  Not system created shares.

Your system share has files on the array. Possibly you enabled Dockers or VMs before installing cache so the images got put on the array where their performance will take a hit due to parity and they will keep array disks spinning.

 

Do you have any dockers or VMs yet?

[Hasodi]

I started the server with no parity or cache.  I copied my data first then added the parity and cache.  The array is currently building the parity.  To prevent slow downs I haven't starts Dockers or VMs yet until the parity check is completed.

 

Since the system shares are on Cache-Prefer, won't they get moved to the SSD eventually?

Edited December 12, 2019 by Hasodi

[trurl]

You have enabled Docker and VM services, so they created their image vdisks on disk1. Disable those services, delete the images, and recreate them so they will go on cache where they belong.

 

It is a common problem when people enable these before installing cache. And mover can't really help by itself because it can't move open files, so the services have to be disabled. Simpler to just go ahead and recreate them at the same time.

[Hasodi]

I did experiment with dockers while I was on the trial version before I put all the hardware together.

 

Ill wait for parity to complete then perform the recommended actions.

 

Thanks for the tips!!