Hi, I'm running fio job with trigger, and using load/save_verify_state to run verify phase afterwards. Both write and read have the same offsets and sizes and both are using non random patterns. >From time to time I see that the fio read verify actually reads offsets bigger than the latest offset in the file saved during write phase. Both workloads are running with iodepth of 300, I wonder if the iodepth affect somehow the end offset during read phase? Could it be that fio during read is reading from last_sector_written + iodepth? Thanks, Roy
