The IOR data verification seed (-G option) is always set to "27". That causes the data pattern written to disk to always be the same, and in case of read error it isn't possible to determine whether the incorrect data read is from the same test run or not. This value should be unique for each test run, though it should be possible to specify this value if e.g. running only ior-hard-read to verify data that was previously written by ior-hard-write.
The IOR data verification seed (
-Goption) is always set to "27". That causes the data pattern written to disk to always be the same, and in case of read error it isn't possible to determine whether the incorrect data read is from the same test run or not. This value should be unique for each test run, though it should be possible to specify this value if e.g. running onlyior-hard-readto verify data that was previously written byior-hard-write.