Hi,

 

I've built up my UnRAID over the last few weeks (at about 14TB now) from a WHS build. The last thing I did was add the cache drive (using UnRAID 4.6 Final by the way). Afterwards, I haven't moved any files into my shares. I do store programs (folder start with '.') at the root of the cache drive (i.e. /mnt/cache/.programs/).

 

What I am seeing is that:

1. Cache mover script (runs once a day for me right now) spins up all drives

2. Mover logging shows that it tries (?) to move all of the files in the folders that start with a '.'

 

Please note: in all of these situations, I've never had any files on the cache drive that required moving. This happens every night.

 

Any ideas why?

Are you running any additional programs like the community addon script "cache_dirs" ? How are your spin-up groups defined, are all disks in the same group?

I am running cache_dirs, but I believe it should be idle apart from the first half an hour or so after reboot when it actually scans all of the folders, no?

 

Also, I have spinup groups disabled.

 

Thanks.

The "mover" script is a fairly simple minded shell script based on "find" and "rsync"

 

It contains a "sync" command that is run at the end of its processing, regardless if files were moved, or not.  That "sync" command will spin up all drives.

 

As far as it attempting to move directories with a leading "."  It is coded to ignore a top level folder only named in that way.... however, the current command is coded in a way where it will print (log) every file and directory folder under /mnt/cache, so that too is to be expected.  That "print" occurs before the exclusion of the directories with the leading "." so it is why they are being logged, even if they are not moved.  (they are being logged and then are being excluded)

If you do not wish the "mover" to spin up the drives you can comment out the "sync" by invoking a line like this

sed -i 's@^sync$@#sync@' /usr/local/sbin/mover

 

You can put that line at the end of the config/go script if you want it to take effect every time you reboot.

It is probably best for you to have a UPS, since without the sync it is possible for the files to be entirely in the in-memory buffer cache until the disk blocks are next written to the physical disk.

 

Joe L.

 

 

 

 

Checkout this thread to see how I eliminated the unnecessary spinups.

The "mover" script is a fairly simple minded shell script based on "find" and "rsync"

 

It contains a "sync" command that is run at the end of its processing, regardless if files were moved, or not.  That "sync" command will spin up all drives.

 

As far as it attempting to move directories with a leading "."   It is coded to ignore a top level folder only named in that way.... however, the current command is coded in a way where it will print (log) every file and directory folder under /mnt/cache, so that too is to be expected.  That "print" occurs before the exclusion of the directories with the leading "." so it is why they are being logged, even if they are not moved.  (they are being logged and then are being excluded)

If you do not wish the "mover" to spin up the drives you can comment out the "sync" by invoking a line like this

sed -i 's@^sync$@#sync@' /usr/local/sbin/mover

 

You can put that line at the end of the config/go script if you want it to take effect every time you reboot.

It is probably best for you to have a UPS, since without the sync it is possible for the files to be entirely in the in-memory buffer cache until the disk blocks are next written to the physical disk.

 

Joe L.

 

Thanks guys. This is really interesting. I think for me, if I want to run the mover script once every 24 hours (as opposed to more frequently), I know for a fact I will have files to move almost every single day, so I like your suggestion Joe L. I do have a UPS on the server, but the only thing it protects from is a quick power surge -- it won't last over 15 seconds I don't think. In any case, how big of an issue are we talking about here? I do have a lot of memory (8 GB), but most of my files are large. How long can the files stay in memory? If it's a day or two, I think I can live with losing some of the files.

 

Thanks a lot for the support!