Hi,

 

I've tried a couple of dockers but always end up stop using them as my disks won't spin down when I do.

 

The docker image is on the cache drive in a "non move" folder (/mnt/cache/.custom/docker).

 

Even with no docker containers running the disks appear to spin up within a minute or two of being manually spun down and stay up.

 

I have all disks set to spin down after 15 mins.

Turn off all dockers. Reboot. Make sure that your appdata folder is on the cache or on some additional ssd drive outside the array. If your cache is a spinner and hosts the appdata folder it might still spin up when the docker reads or writes config settings or logs. And this you can't prevent in most cases.

 

Enable the first docker. Check if it is spinnung up something. If so check all settings of this dockers app.

 

If you have dockers like plex that check for library updates regularily you should turn that off or reduce the rate in their settings or all disks which belong to your libraries will spin up, when a check occurs. Nzb or torrent apps checking specific folders for new nzbs or torrents will also spin up your disks if those are located on the array or a spinner drive. Of course disabling such things will take some convenience away. So having spindown comes with a price.

 

Once you have setup the first docker to not spinup anything besides your cache or appdrive ssd, go on to checking the next one.

thanks for the reply.

 

I've been monitoring this for the last week after rebooting the server.

 

It all seemed fine but now its doing the same thing.  The mover ran last night and then there was only a spindown command for the parity drive.  The others were all running.  I used the manual spindown buttons on the gui and left for work, I'll see what its like when I get home.

 

Is there a way of seeing what the OS thinks is active and is keeping the spindown command from being actioned?

There is inotifywait. Sadly the messages it generates don't always give away what is really the issue. But it's worth a try.

 

To track activity under /mnt/user  (all the user-shares), type:

inotifywait -mr /mnt/user

To track activity on a specific disk (/mnt/disk1), type:

inotifywait -mr /mnt/disk1

 

If you have a lot of files under /mnt/user you might need to increase the "default" number of files watched by typing:

echo "500000" >/proc/sys/fs/inotify/max_user_watches

There is a plugin called openfiles. This will show which files that are open that would prevent your disks from shutdown. 

 

https://lime-technology.com/forum/index.php?topic=42881.0

Thanks, I'll have a look at both of those over the weekend...