The subject line says it all.  I had been running 5.0rc-16 for over 6 months without any issues involving the auto-spin down of my drives.  However, since upgrading to v5.0.5, my cache drive no longer spins down (data+parity drives are fine). 

 

Note: I have the "spindown delay" for the cache drive set to 15 minutes.

 

Any suggestions as to which settings I should be looking at?  What additional information would be useful to help diagnose the issue?

 

Thanks!

are you running any plugins that are set up as Applications on the cache drive? Plex, torrents, netnews, etc.

What do you get when you do

lsof /mnt/cache

 

I ran the 'lsof' command as you indicated, and there was no output displayed.

install inotifywait. There is an unmenu package.

 

Here is another observation:

 

- If I manually spindown all drives, the cache drive spins back up the moment I close my browser window (using Dynamix Web GUI).  I checked my syslog, but I'm not showing any activity after the manual spindown:

 

Feb 11 13:25:10 fortress emhttp: Spinning down all drives...

Feb 11 13:25:10 fortress kernel: mdcmd (59): spindown 0

Feb 11 13:25:11 fortress kernel: mdcmd (60): spindown 1

Feb 11 13:25:11 fortress kernel: mdcmd (61): spindown 2

Feb 11 13:25:11 fortress kernel: mdcmd (62): spindown 3

Feb 11 13:25:12 fortress kernel: mdcmd (63): spindown 4

Feb 11 13:25:12 fortress kernel: mdcmd (64): spindown 5

Feb 11 13:25:13 fortress emhttp: shcmd (8264): /usr/sbin/hdparm -y /dev/sdf &> /dev/null

 

Test without any add-ons.

I booted into 'Safe Mode' and noticed the same behavior (i.e. once I manually spindown all drives and close the web GUI, the cache drive spins back up). 

 

I'm going to try using v6-beta3 later today to see if that makes any difference.

 

2/14/14 Update: I'm having the same problem with v6beta-3.  Has anyone else experienced this problem with their cache drives spinning back up after a manual spin down?