Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google

Our Sites

covecube.com 
community.covecube.com 
blog.covecube.com 
wiki.covecube.com 
bitflock.com 
stablebit.com 

Poll

No poll attached to this discussion.

In order to better support our growing community we've set up a new more powerful forum.


The new forum is at: http://community.covecube.com


The new forum is running IP.Board and will be our primary forum from now on.


This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.


Thank you,

problem with drivepool taking over server resources

edited October 2011 in DrivePool

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?

 

Comments

  • Covecube
    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.
Sign In or Register to comment.