Jump to content
  • 0

Statistics are incomplete


LindsayCole

Question

Hi All,
 
 I recently added 4 new 2TB drives to my array, and now statistics and balancing do not seem to be happening properly anymore.

 

 I have done the troubleshooting and reset all settings, but it always seems to stop calculating at about 10TB into the 38TB.

 

Any suggestions?

 

Thanks,

Link to comment
Share on other sites

16 answers to this question

Recommended Posts

  • 0

I'm very glad to hear it!

And I'm not surprised that this fixed it. Specifically, we changed how some of the code works to measure the pool, as well as re-ordered some of the priorities of different sections.  Between these changes, it most likely fixed the issue, where ever it was getting hung up on.

 

If you need anything else or have any questions, don't hesitate to ask!

Link to comment
Share on other sites

  • 0

... That would definitely be an issue. 

 

 

To make sure, this is with the beta build (2.2.0.625)?

If so, could you enable file system logging, and remeasure?

http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection

 

 

And could you get a dump of the UI and Service if this happens again?

http://wiki.covecube.com/StableBit_DrivePool_Service_Memory_Dump

http://wiki.covecube.com/StableBit_DrivePool_UI_Memory_Dump

 

 

After doing that, would you see if resetting the settings helps?

http://wiki.covecube.com/StableBit_DrivePool_Q2299585B

Link to comment
Share on other sites

  • 0

Unfortunately, the log files you've posted don't have the tracing logs.

There should be a "CoveFS" folder, and it should have contents listed in there (elt files, I beleive).

 

If needed, stop the service, grab the files and start it back up. (this can be done using "services.msc" and finding the "StableBit DrivePool Service" and right clicking on it).

 

Also, it does look like you removed a drive that was failing recently. Or at least attempted to:

\\?\Volume{ee759062-7a84-11e4-80ba-00155d010400}\PoolPart.81396a7d-b382-404d-9ab6-45d5b333ed39

 

You can run "mountvol X: \\?\Volume{ee759062-7a84-11e4-80ba-00155d010400}" to see which drive this is, if it's still attached.

Link to comment
Share on other sites

  • 0

There we go. Sorry for the delay.

 

All three have been uploaded. I referenced this thread in the notes. I can replicate the line outside of the bar on command.

 

If you guys need a closer look, I can facilitate access to the system as needed. I look forward to your response.

 

Thanks!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...