Hi, Feel free to switch - I think we've got enough to investigate the bug you were seeing. On 31 October 2017 at 23:09, David Hare <david.hare@xxxxxxxxxxxxxxx> wrote: > Ok, its easy for me to switch OS's let me know, when you have something > ready. > -Dave > > -----Original Message----- > From: Sitsofe Wheeler [mailto:sitsofe@xxxxxxxxx] > Sent: Tuesday, October 31, 2017 4:06 PM > To: David Hare <david.hare@xxxxxxxxxxxxxxx> > Cc: Jens Axboe <axboe@xxxxxxxxx>; fio@xxxxxxxxxxxxxxx > Subject: Re: FIO windows > > OK I see the problem too when using this on Windows: > $ ./fio --size=1g --filename > fio1.tmp:fio2.tmp:fio3.tmp:fio4.tmp:fio5.tmp:fio6.tmp:fio7.tmp:fio8.tmp:fio9.tmp > --name=go --create_only=1 > $ ./fio --size=250m --filename fio1.tmp:fio2.tmp:fio3.tmp --name=go > --direct=1 --bs=64k --runtime=1m --time_based --thread > > Using --debug=all shows the following: > io 2796 getevents: 1 > io 2796 io complete: io_u 0000000007BD8F00: > off=87359488/len=65536/ddir=0io 2796 /fio3.tmpio 2796 > file 2796 put file fio3.tmp, ref=2 > file 2796 trying file fio1.tmp 11 > file 2796 goodf=1, badf=2, ff=11 > file 2796 get_next_file_rr: 00007FF5FEEA4610 > file 2796 get_next_file: 00007FF5FEEA4610 [fio1.tmp] > file 2796 get file fio1.tmp, ref=1 > io 2796 fill_io_u: io_u 0000000007BD8F00: > off=21846/len=65536/ddir=0io 2796 /fio1.tmpio 2796 > io 2796 prep: io_u 0000000007BD8F00: > off=21846/len=65536/ddir=0io 2796 /fio1.tmpio 2796 > io 2796 queue: io_u 0000000007BD8F00: > off=21846/len=65536/ddir=0io 2796 /fio1.tmpio > helperthread 2796 > 2796 since_ss: 0, next_ss: 1000, next_log: 495, msec_to_next_event: 136 > file 2796 put file fio1.tmp, ref=2 > io 2796 io_u_queued_complete: min=0 > io 2796 getevents: 0 > process 2796 pid=2936: runstate RUNNING -> FINISHING > fio: pid=2936, err=22/file:ioengines.c:335, func=td_io_queue, error=Invalid > argument > > off=21846 is not a multiple of 512. > > $ du -b fio*tmp > 119304647 fio1.tmp > 119304647 fio2.tmp > 119304647 fio3.tmp > 119304647 fio4.tmp > 119304647 fio5.tmp > 119304647 fio6.tmp > 119304647 fio7.tmp > 119304647 fio8.tmp > 119304647 fio9.tmp > > I think this is all hinting at a bug in fio (perhaps when working with > multiple pre-existing files that are bigger than size specified) but I think > I'm done for the day... > > On 31 October 2017 at 22:51, David Hare <david.hare@xxxxxxxxxxxxxxx> wrote: >> >> Not sure what you mean by one file? The drives are local NTFS >> formatted with Allocation unit size of 64k, they range in size from with >> are 186gb - 372gb. > > -- > 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
