Hi, On 31 October 2017 at 20:46, David Hare <david.hare@xxxxxxxxxxxxxxx> wrote: > > If I remove - "blocksize=64k" "direct=1" "thread=8" "size=1g" "time_based > with runtime=10" or ":P\:\\testfile:" (the 9th drive) the file works. > > The below file generates this error: > fio: pid=8404, err=22/file:ioengines.c:333, func=td_io_queue, error=Invalid > argument > asdf: (groupid=0, jobs=1): err=22 (file:ioengines.c:333, func=td_io_queue, > error=Invalid argument): pid=8404: Tue Oct 31 > > > [global] > > ioengine=windowsaio > blocksize=64k > direct=1 > > thread=8 > size=1g > > time_based > runtime=10 > > [asdf] > filename=F\:\\testfile:G\:\\testfile:H\:\\testfile:I\:\\testfile:J\:\\testfile:K\:\\testfile:L\:\\testfile:M\:\\testfile:P\:\\testfile: "thread=8" should be the same as using "thread" and would be required on Windows. "P\:\\testfile:" should be "P\:\\testfile" (note the lack of trailing colon - see the examples in http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-filename ). time_based and runtime sound required. Perhaps a smaller blocksize means it takes longer than 10 seconds to hit the problem - presumably blocksize=128k is still as problematic? I'm also assuming the problem still happens with size=512m ? -- 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
