Pichu0102 Posted April 2, 2016 Share Posted April 2, 2016 I was wondering, when Scanner triggers an evacuation of files, for files already duplicated elsewhere on the pool, does it pull and duplicate copies from healthy drives, or from the unhealthy drive? Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted April 2, 2016 Share Posted April 2, 2016 It does pull the files from the "unhealthy" drive. For the most part, this shouldn't be an issue at all, as most of the data should be healthy and intact. It's just the affected data that is problematic, and it could affect more data. And IIRC, when moving files around, we use the same API call that Explorer uses (when you're dragging files around or copy/pasting them). If it runs into errors, we do flag the files in the UI, and continue on moving out files that can be moved. If you're exceptionally concerned about this, you can enable the "verify after copy" option, which performs a compare when moving or copying files: http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings Set the "DrivePool_VerifyAfterCopy" setting to "True", and restart the service (or reboot the system). However, you may get some errors here, as occasionally, the thumbs.db files can get out of sync n the different drives, based on how they're created. And this will slow down the balancing (evacuation), as well. Quote Link to comment Share on other sites More sharing options...
Question
Pichu0102
I was wondering, when Scanner triggers an evacuation of files, for files already duplicated elsewhere on the pool, does it pull and duplicate copies from healthy drives, or from the unhealthy drive?
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.