On Fri, Aug 2, 2013 at 2:21 PM, Juan Casse <jcasse@xxxxxxxxxx> wrote: ... > Grant, if fio currently has lfsr and the breadcrumbs and can do writes > with do_verify=0 and reads with do_verify=1, it seems to me that fio > already satisfies our requirements for data integrity testing, That's almost true. :) > contingent on Jens' answers to my questions above. Also, wouldn't > these features be sufficient for data retention testing as well? Yes, they will be once you implement them. E.g. numberio is not a generation number. Given the LFSR seed, one could determine the generation number. So perhaps add the LSFR seed value to the data structure so that gets written with each test run many many times too. Later, when we validate the drive, we can determine generation number and confirm the value is correct that was read from media. All of this needs to be implemented. Carefully re-read Jen's replies. Some of his answers are "speculative" (e.g. "could do this" vs "does this"). > If you write do_verify=0 and then 3 months later read do_verify=1, > wouldn't that be enough? Correct - That's the goal. It's not reality yet. :) cheers, grant -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
