[Should "System Volume Information" and "Recycle.bin" folders be excluded? +UI issues]

...

As for the pie chart, usually running the "Remeasure" option fixes most issues with it. As for why it didn't right away, do you have RealTime duplciation disabled?

 

As for the Scanner process, could you get the Error Reports from Scanner?

WHS: http://wiki.covecube.com/StableBit_Scanner_for_WSS_Error_Reports

WIndows: http://wiki.covecube.com/StableBit_Scanner_for_Windows_Error_Reports

 

No, Realtime duplication is active.  Also, the balance immediately option is enabled.

 

I've sent in the reports.

 

Thanks

 

--Bill

[Should "System Volume Information" and "Recycle.bin" folders be excluded? +UI issues]

I have one drive pool that is set for 2x file duplication.  I noticed that when I went to folder duplication, I could exclude specific folders from duplication, so I did so with .System Volume Information and $RECYCLE.BIN.  Now I'm wondering if I should have done that for .System Volume Information.  What is the best state for both of these?  I thought that the size SVI can grow too would just be a pool space waster...

 

I'm using the v2 release version of DrivePool and have noticed several different UI issues.  One time, after removing a 3T drive (not forced) and replacing it with a 4T (in a pool with 1 other 3T and 4 other 4T's) that the pie chart showing divisions of assets (!) was fully closed but also showed 5.99T free in text above it after the new drive was inserted.  I tried several things including a reboot and nothing corrected it.  Then I removed the second 3T drive to replace it with a 4T (so now there are 6 4T's) and right after I put the new 4T in, the page redrew and the pie chart was corrected.

 

However, the chart showed about 900G unduplicated and did NOT start a duplicating pass.  (I have the duplicate option set to immediate).  After an hour it still hadn't done anything, so I selected the Remeasure option.  At that point duplicating started right up.

 

A quirk or a bug?  I'll switch over to the recent beta's of DP and Scanner and see if anything changes.

 

Also several occasions where the UI for Scanner went south (saying Not Responding).  I had to kill the Scanner process, but then everything came back operational.

 

--Bill