[File Placement for New Drives]

The new version won't keep the box ticked either.

 

Otherwise, everything is working great!  

["Filesystem Damaged" but chkdsk reports no issues]

The issue has returned!  Here's the contact URL i was provided.

 

http://stablebit.com/Contact/2052158

[File Placement for New Drives]

I have added a new drive to my pool, and I can't seem to get DrivePool to reshuffle the files to use the space evenly (for balancing).  I have tried ticking the "When a new drive is added to the pool, files matching this rule should be placed on that drive" but it doesn't stay ticked.

 

How can i:

1.) Force a re-balancing pass, and

2.) Have DrivePool re-balance all my files to use the new disk?

 

It should be mentioned I've noticed new files do get written to the disk as expected when using the pool. 

 

This is version 2.2.0.651 Beta running on Windows Server 2016 Standard.

 

EDIT: I was able to get this to behave how I want via the "Disk Space Equalizer" plugin.  I'm still curious why I can't tick the option I mentioned above, though.

["Filesystem Damaged" but chkdsk reports no issues]

Thank you so much!

 

Aaand, just like that...the filesystem checks healthy this time.  I'll leave things as they are for a bit and see if it reports anything else.  If so, I'll upload as instructed.

[Scanner can't detect drives in Storage Spaces]

I found that ReFS on a storage space was EXTREMELY slow compared to DP.  I was seeing disk latency in the 4+ seconds.  Using NTFS resolved the issue, but defeats the purpose of what I was trying to accomplish, so I moved back to DP + SnapRAID.

 

I do *really* miss shadow copies, but it's worth it to have a fast pool.

["Filesystem Damaged" but chkdsk reports no issues]

No, I'm running a "chkdsk e: /f".  It reports no issues.

 

Could the volume be too big for the scanner to understand?

["Filesystem Damaged" but chkdsk reports no issues]

I have a Gen3 Drobo (USB 3.0) with a 64TB thin volume that the scanner reports has a damaged filesystem.  Chkdsk reports no issues.  Why would the scanner report in this way?  How can I ensure there isn't any filesystem damage if this is a false positive?

[Windows Server 2012 R2 Share Quotas Unable to set]

Sure!  It's in the "File Server Resource Manager" snap-in, along with disk quotas.  See screenshot

 

 

[N00b questions about duplication/recovery]

Not to hijack the thread, but I have an add-on question to the OP's original question.

 

If I am *not* duplicating everything, how will I know which files are missing if a disk fails?  Any chance you could build in some rudimentary reporting or something to that effect?

[Windows Server 2012 R2 Share Quotas Unable to set]

To add to this request, I'd also like to see this implemented as I expect it will also allow the "File system screening" option to work (it currently fails with the same error message).  We use it to block the creation of specific files and file types on our file shares, and it's a fairly critical feature for us.