I am on unRiad 6.12.4.

20TB X 3 HDD for DATA

20TB X 1 HDD for Parity

2TB x 1 NVME for cache

 

Queries 

1).

primary storage is "Cache" and secondary is "Array".

"Mover action" set to Cache → Array

Which files will mover move ? I mean Oldest first ?  or First comes first move ? or by other rule ?

 

2).

primary storage is "Cache" and secondary is "Array".

"Mover action" set to Array → Cache

      2A). Again., Which files will mover move ?

      2B). Will mover moves file from array till cache becomes full ?

      2C). If two or more shares having same Array → Cache action set for mover then, how to decide which share will have more cache space allocated after move ?

 

3). I do assume Movers moves files like cut + paste. Or it behaves like copy + paste ? or in deferent scenario behaves differently ?

 

4). if first share having mover action set to Cache → Array and other share having mover action set to Array → Cache then because of second share cache remains always full and no  new cache space remains for first share after move ?

 

forgive me if I am taking mover behaviour totally wrong. But after reading WebGUI's suggestion strings I left with lots of confusions. 

Mover always moves ALL files from the share from the source to destination, until the "Min free space" is reached.

 

There's a Mover Tuning plugin that gives you a few more options so have a look at that.

Edited September 27, 20232 yr by Kilrah

1 hour ago, kalind said:

3). I do assume Movers moves files like cut + paste. Or it behaves like copy + paste ? or in deferent scenario behaves differently ?

Not quite sure what you mean by this?   Mover uses a copy/delete strategy.   Also it will not overwrite files that already exist on the target as this should never happen in normal operation.

1 hour ago, kalind said:

4). if first share having mover action set to Cache → Array and other share having mover action set to Array → Cache then because of second share cache remains always full and no  new cache space remains for first share after move ?

 

Yes.     

 

You would ideally only set array->cache for shares that are small enough to be held completely on the cache and that you want on the cache for performance reasons.