Quick-Validate vs Validate vs Verify


Quick-Validate is more of a quick change reporting task that an actual RAID health validation task.
All it does is detect and report changes (looks for files deleted or changed).

It was created:

  • for doing quick checks before running the Validate task or Verify task (if Quick-Validate reports changes, so will these tasks)
  • for users wanting to script FlexRAID (determine the next action based on the reporting of Quick-Validate)

True health validation is done through the “full” Validate task or the Verify task.
Note that the Update task has a Quick-Validate logic built into it, and it certainly does not make sense to schedule a Quick-Validate before running it (outside of special scripting logic).


The Validate task does both change detection along with datarot (silent data corruption) detection through data checksum valiation.


The Verify task does bit for bit verification of the RAID.

Be Sociable, Share!


2 Responses to “Quick-Validate vs Validate vs Verify”

  1. Freaksta June 6, 2011 at 8:08 AM #


    I remember once seeing an article about the 3 different things the one thing i’ve forgotten is how to identify if there are data changes? When it just says 100% complete on quick-validate does that mean that there have been changes? My next question is once that has happened how do you identify which drive the changes have been made to?

  2. Simon March 23, 2015 at 4:22 AM #


    detection with datarot (silent data corruption) … how does flexraid decide where is datarot? In the active storage pool or in the backup? Maybe the datarot is in the backup … ???


Leave a Reply