New data saving to array and not cache drive (SOLVED)

[ados]

As to not create another thread I thought to add my question to this one.

I have noticed my cache drive has stopped working for one share only which is set to 'yes'

There are two issues:

• Some files were stuck in the cache drive regardless of the amount of 'move requests'
• All new files go to the array and bypass the cache drive

I played around with enabling and disabling the cache setting on the share but no luck

 

I thought I could fix it by disabling the cache setting on the share and deleting the corresponding top down folder with that share name as the remaining files were few and had little value. The share then changed to the green color indicating no link to the share (seemed good) and then enabled the share to use the cache drive but it did not create the directory expected.

 

Then when I complete more tests there was no caching, all files to the array and more so the array would no longer stop with the cache drive halting the process until I disabled the cache setting on the share.

 

I decided to create the top directory myself and test further but it never saves to the cache drive and never makes any sub folders

I then tested this with a new created test share and with a few sub directories everything worked perfectly

At this point I'm thinking the share needs to go but I cannot loose the mountain of data within it and you cannot delete the share without deleting the data. Is there a better way to fix this, thanks in advance.

[JorgeB]

Split to a new topic since it has nothing to do with the one where you posted on.

 

Make sure mover logging is enable (Settings -> Scheduler), run the mover and post the diagnostics: Tools -> Diagnostics

[ados]

Ok, thanks

[ados]

Dang I feel bad for creating another thread. To my defense its easy to read that as an instruction without the 'I'.

Just ran two moves but there is nothing to move at the moment

unraid-diagnostics-20200403-2036.zip

[JorgeB]

1 hour ago, johnnie.black said:

Make sure mover logging is enable (Settings -> Scheduler),

 

[ados]

unraid-diagnostics-20200403-2109.zip

[JorgeB]

There's nothing to be moved, what's the share name you're trying to move from?

 

 

[ados]

Faulty share: PlexMedia

 

Just conducted a test. Test.txt file copied to PlexMedia and test shares.

The PlexMedia went straight to the array despite 'yes' set on the share

test share worked perfectly

unraid-diagnostics-20200403-2119.zip

[JorgeB]

Share minimum space for the PlexMedia share is set to 500GB, more than it's available on cache, so it goes directly to the array.

[ados]

I thought thats the purpose of this setting, otherwise how does one not red line their larger drives

[ados]

F#%@ that was it, must have changed it at some point and forgot. I think I was trying to stay at 90% on my drives, is that possible with a cache drive

[JorgeB]

The larger value of the two will take precedence, 500GB is lot to leave free for the array disks, you could set the Plex share to 50GB also.

[ados]

Seems like UNRAID needs a feature to fill this I think.
I do appreciate your help with this, close at your leisure.

[JorgeB]

There was a recent request for the same thing, you can add to that, the more positive comments a feature request gets the more likely to be implemented by LT.