Thanks. Using --output on the command line will work for my simple example. However, if I make two jobs in one file, then the --output parameter forces all output into one file. [test_job] ioengine=libaio direct=1 rw=randread iodepth=1 size=100% numjobs=1 bs=4k filename=/dev/nvme0n1 runtime=10s time_based output=test_job [test_job2] ioengine=libaio direct=1 rw=randread iodepth=2 size=100% numjobs=1 bs=4k filename=/dev/nvme0n1 runtime=10s time_based output=test_job2 Maybe it's best to make one job file per fio job. Regards, Jeff -----Original Message----- From: Ruvinsky, Konstantin [mailto:Konstantin.Ruvinsky@xxxxxxxx] Sent: Wednesday, May 3, 2017 10:43 PM To: Jeff Furlong <jeff.furlong@xxxxxxx>; fio@xxxxxxxxxxxxxxx Subject: RE: fio output parameter Hi, You can use the following: fio --output kuku.log test.txt and remove output from the job file Regards Konstantin -----Original Message----- From: fio-owner@xxxxxxxxxxxxxxx [mailto:fio-owner@xxxxxxxxxxxxxxx] On Behalf Of Jeff Furlong Sent: Wednesday, May 03, 2017 11:59 PM To: fio@xxxxxxxxxxxxxxx Subject: fio output parameter Hi All, When in command line mode, the output parameter dumps the output to a file. When in job mode, the output parameter cannot be used, so all output goes to stdout. Can the output parameter be used with job files? Consider below: # fio -version fio-2.19-59-gf52e9 #fio --name=test_job --ioengine=libaio --direct=1 --rw=randread --iodepth=1 --size=100% --numjobs=1 --bs=4k --filename=/dev/nvme0n1 --runtime=10s --time_based --output=test_job #cat text.txt [test_job] ioengine=libaio direct=1 rw=randread iodepth=1 size=100% numjobs=1 bs=4k filename=/dev/nvme0n1 runtime=10s time_based output=test_job # fio test.txt Bad option <output=test_job> Regards, Jeff -- 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 -- 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
