I'm seeing numerous instances of my parity drive spinning down in my syslog. I do not have a chache drive and there were no writes to my server in the same timeframe so the parity drive never should have spun up in the first place. I think it may be associated with a XMBC client accessing the library but I'm not 100% sure. How can I find out what is causing the parity drive to spin up? Syslog is attached.

syslog-2012-09-29.txt

I'm seeing numerous instances of my parity drive spinning down in my syslog. I do not have a chache drive and there were no writes to my server in the same timeframe so the parity drive never should have spun up in the first place. I think it may be associated with a XMBC client accessing the library but I'm not 100% sure. How can I find out what is causing the parity drive to spin up? Syslog is attached.

See here:

http://lime-technology.com/forum/index.php?topic=17449.msg157730#msg157730

 

If the parity disk is spinning up, it is either in a spinup group shared with another data drive, or, a data drive is being written.

 

Joe L.

I had already checked the spinup groups possibility and I do not have spinup groups enabled so it must be due to something writing to a data disk. I've got inotify running now I'll just have to wait and see. Thanks Joe.