Prabhu, As Jeff mentioned you weren't specific as to exactly what went wrong. Additionally - did you read all the text for the number_ios option over on http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-number-ios especially the following: "Note that this does not extend the amount of I/O that will be done". On 22 November 2017 at 23:06, Jeff Furlong <jeff.furlong@xxxxxxx> wrote: > What parameters are you using? Here is a counterexample from a previous post that shows number_ios running and then the job terminating: > > fio --name=test_job --ioengine=libaio --direct=1 --rw=read --iodepth=1 --size=100% --bs=4k --filename=/dev/nvme1n1 --number_ios=8 > > Regards, > Jeff > > -----Original Message----- > From: fio-owner@xxxxxxxxxxxxxxx [mailto:fio-owner@xxxxxxxxxxxxxxx] On Behalf Of Prabhakaran > Sent: Wednesday, November 22, 2017 2:47 PM > To: fio@xxxxxxxxxxxxxxx > Subject: Running for a specific number of IOs > > Hi, > > Is there a parameter in FIO that can be used to run for a specific number of IOs? I thought 'number_ios' might to this, but actually it does fill 1x of the drive usable space and exits. > > Thanks, > Prabhu -- 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
