So, using his post as guide i seted up my mover scrip to check every 5 mins if any new data was added to the cache drive. If so, and the data drives have been idle for 10 or 15? mins the script start moving data from cache to the shares according the allocation method.

 

When i moved bigger files / folders took more than 5,10 or even 30 mins so i ended up writing the data on the cache drive, reading from the cache and writing in the data drives and parity drives. So all this defeats the cache purpose in my opinion. Would be possible modify the mover script to check every 30 mins instead of 5? I mean i know it is possible, but that would make any sense? Does anyone have the same problem?

 

Would all this writing / reading operations defeat the cache drive purpose?

 

Thanks in advance!

 

 

Any idea how can i modify this to make it check the cache drive every 30 mins instead 5 min??

 

 

 

Any idea how can i modify this to make it check the cache drive every 30 mins instead 5 min??

The schedule is a "crontab" entry.

 

Instead of

*/5

at the front of the string you enter

put

0,30

or

*/30

 

The last two would be functionally identical.

Joe, any downside to running the mover script too often?  Every 5 mins seems excessive to me.

Joe, any downside to running the mover script too often?  Every 5 mins seems excessive to me.

 

I did have it running every 5 mis for the past week (not too long i know) and i didn't have any problem at all. Beside mover check every 5 mins if there is no read / write in the data disk before start moving data from the cache drive. I did ask JOE how modify one thing because when i first try it the disk never spun down because the mover was keeping the disk always spinning. After that no problem at all. Not sure what more advanced users have to say about it.

 

The only problem for me was what i wrote in the beginning of the thread.

Joe, any downside to running the mover script too often?  Every 5 mins seems excessive to me.

Only one "mover" script will run at a time.

The modified script he is describing is waiting for all disk I/O to cease for 10 minutes before kicking off the "mover"

This minimizes any effect it might have of you playing music/movies.  If there is nothing to move, nothing happens.  If the disks are busy, nothing happens.  It just means the first opportunity possible, when all disks are idle, a file written to the cache drive will be copied to the protected array. 

 

This may be the wrong logic for many people.  The mover may never run if some disks are always having I/O.  You need to know how you are using your server to decide.

Interesting.  I was thinking that there might be some kind of 'wear and tear' concerns, but I guess the only thing affected would be increased reads on the flash drive.

Works like a charm for me. I mostly use it for media back up file for my photography business so i am not writing / reading data 24/7