problem with drivepool taking over server resources

koherp

I have been having this issue recurring several times in the past week or so where drivepool just totally takes over the server resources (98-100% CPU, 1-1.5GB memory) for an extended period of time , which basically prevents the server from being a server - no access to shares, streaming, utorrent seeding etc. Rebooting the server seems to get things back in order.   This occured on build 4035(or whatever the current build was about 2 weeks ago).  After a few incidents, I headed here yesterday to get a later build (4070) but the problem recurred again today. 

WHS2011 is a fairly new install (2 weeks or so), drivepool config is pretty basic (no folder duplication, only 2 disks in pool) and only programs on server are advanced admin console,utorrent + twonky server

questions I have: (primarily directed at developers but users feel free to chime in too)

-anyone else experiencing anything like this? 

-are there are any known contributing factors to this? ie persistent disk I/O(utorrent)? massive numbers of small files etc? 

-should I be uploading the service log reports after each "bog down incident"?  I have done this a few times but I don't if its actually worthwhile since its not technically a crash or error?

 

Alex

I haven't seen this with the tests that I'm doing locally. DrivePool is up for weeks at a time with no visible problems.

The way to troubleshoot this is to take a dump of the DrivePool service using task manager. But with the changes coming to M4 I don't think this is necessary.