Hi to everyone.

Probably someone already asked this question, but googling, i can't find something related to my problem. 

 

I've a very easy problem, and i mostly need to understand if there is a solution, or if unRaid is made in that way and i can't change this behaviour. 

 

I keep most of my share cached, and i move my share one to week, mostly because i love the ability to have my new file available without the need to spin up drives. (I would probably get a parity cache in future)

 

I noticed that every time i make a new folder on a share or disk that is cached, the parity drive spin up. It is normal?

 

I've been working with this problem for almost two years, from my first unRaid setup, never asked question, but now i've upgrade unRaid and i'm using the new "Backup/Restore Appdata" plugin from Robin Kluth, very good plugin, before every backup was stored on a .rar archive, now it makes a new folder for every backup, and it's stupid that i need to spin up the parity drive just to make one folder, for a backup that need less than 1 minute, when the drive still up for 1 hour. 

 

 

 

Thanks for the help.

up

 

So no one know the solution, i can assume it's a problem and not something normal. The i would stop doing backup to appdata. Easy solution. 

Having duplicate files on both the cache and array would spin up parity.  Check to make sure there are no files having the same name that exist in the same path on different disks.