RE: FIO windows

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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/

��.n��������+%������w��{.n�������^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�

[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux