On 04/10/2014 09:56 AM, Carino, Mario wrote:
Here's the job file: [4ktest] fallocate=1 direct=1 rw=randwrite refill_buffers norandommap randrepeat=0 size=2G bs=4k iodepth=16 numjobs=16 runtime=60 group_reporting This job file was created based on a sample command line I was given: fio --filename=/oradata2/o18g2/IO/fiotest4 --direct=1 --rw=randwrite --refill_buffers --norandommap --randrepeat=0 --size=2G --bs=4k --iodepth=16 --numjobs=16 --runtime=60 --group_reporting --name=4ktest I think I understand enough that I need to run a rw=write job first before running the above job, correct?
No, you should not have to run rw=write first, you can run it as-is and fio should setup the files appropriately.
Can you try and delete any leftover 4ktest.* files from the job, and then re-run the job and add --debug=file? Then just break it when it starts going and send the output in a reply here.
-- Jens Axboe -- 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
