dr_no

If I run "Check Duplication Consistency", it completes in only a few minutes on my 3.5TB + 3.5TB duplicated pool. It can not possibly be verifying bits (or even checksums) of the files that quickly. I would think it could only verify that a duplicated file does exists in that amount of time. How do I run the true duplication pass or can I schedule one to run periodically? I am more interested in data integrity than speed. A "DrivePool_VerifyOnRead" setting would be a neat feature. Thanks.

Can Drivepool (or Scanner) verify each bit of the duplication? Kind of like what Scanner does on the hard drive surface, but instead verify that the duplication actually still matches the original bit for bit. This could help determine and possibly correct for bit rot. Maybe this is already a feature? Would this even be as useful as it sounds?