Hi, Can you add unlink=1 and keep reducing the size parameter (e.g. down to 128m then down to 16m then down to 4m then down to 1m then down to 512k etc)? Can you attach the full output that's produced it fails with this reduced job? IF you are make the problem happen with very little I/O being done (i.e. the job bombs out after doing less than 1MiBytes worth of I/O) you can try adding --debug=all to the job and seeing if that offers any clues as to what the last thing it was doing was? On 31 October 2017 at 21:46, David Hare <david.hare@xxxxxxxxxxxxxxx> wrote: > It was ok with or without the colon, the size didn’t seem to make a > difference, but blocksize did.. see the commented block sizes below. > > fio2.fio > [global] > > ioengine=windowsaio > > ;blocksize=64k - error > ;blocksize=32k - error > ;blocksize=16k - no error > > blocksize=16k > > direct=1 > > thread > > size=512g > > > > time_based > runtime=10 > > [asdf] > filename=F\:\\testfile:G\:\\testfile:H\:\\testfile:I\:\\testfile:J\:\\testfile:K\:\\testfile:L\:\\testfile:M\:\\testfile:P\:\\testfile > > Results: > Run status group 0 (all jobs): > READ: bw=141MiB/s (148MB/s), 141MiB/s-141MiB/s (148MB/s-148MB/s), io=1413MiB > (1481MB), run=10001-10001msec > > > -Dave > > > > -----Original Message----- > From: Sitsofe Wheeler [mailto:sitsofe@xxxxxxxxx] > Sent: Tuesday, October 31, 2017 2:28 PM > To: David Hare <david.hare@xxxxxxxxxxxxxxx> > Cc: Jens Axboe <axboe@xxxxxxxxx>; fio@xxxxxxxxxxxxxxx > Subject: Re: FIO windows > > 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/ > > > Disclaimer > > The information contained in this communication from the sender is > confidential. It is intended solely for use by the recipient and others > authorized to receive it. If you are not the recipient, you are hereby > notified that any disclosure, copying, distribution or taking action in > relation of the contents of this information is strictly prohibited and may > be unlawful. -- 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
