Hi, On 1 August 2018 at 18:06, Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx> wrote: > As far as I understand, verification in the multi-threaded (num_jobs > 1) > case is neither supported nor recommended. > > I wonder if it also holds for the case of a multiple-threaded job being run > against a partitioned (using FIO's offset split machinery) device, with > thread per partition. Partitioning like this should very much avoid any > inter-thread overlap, and seems to be safe to run in verify mode. I will > appreciate a comment on whether the simple reasoning above holds, or > something extra still needs to be done. If you can arrange for each "numjob" to write only to a region not touched by any other numjob/job then you can get a meaningful result. For example when fio is generating unique files for each numjob by itself there shouldn't be any problem (or warning). I guess another example would be using filename so all numjobs are using the same file but also using offset_increment (http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-offset-increment ) and an appropriate size together... -- Sitsofe | http://sucs.org/~sits/ -- 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
