Hi there, This is a followup question - the attached sample job file, I could run it successfully on linux but on Windows, even though the files are created, fio never exit. I tried same test on local system directory on Windows, the same situation. Does anyone know why? Thanks! ; Keep adding 1024kb/s reading clients at 4 seconds [global] size=32m rw=read directory=C:\Users\xxxx\test rate=1250 #ratemin=1024 [file1] startdelay=0 [file2] startdelay=4 [file3] startdelay=8 [file4] startdelay=12 [file5] startdelay=16 [file6] startdelay=20 [file7] startdelay=24 [file8] startdelay=28 [file9] startdelay=32 [file10] startdelay=36 On Mon, Jan 14, 2013 at 9:21 AM, Hong Jiang <hong@xxxxxxxxxxxxxx> wrote: > Thanks for all the suggestions. Yes I did observe files being > created. I will play more with it taking your inputs. > > On Mon, Jan 14, 2013 at 1:09 AM, Jens Axboe <axboe@xxxxxxxxx> wrote: >> On 2013-01-11 20:24, Hong Jiang wrote: >>> Hi there, >>> >>> I am pretty new to this tool, and currently evaluating it on both >>> linux and windows platforms. Would appreciate if someone shows me an >>> example of job file that can test this scenario: >>> >>> I have a share that's created out of the "cloud", on windows client >>> side it's mounted as a new drive, on linux it's mounted to a >>> directory. I would like to run some file op tests against the share. >>> >>> I tried to use the example job file that came with the package - >>> 1mbs_clients, modifying the "directory" parameter setting in the file, >>> but I am not sure it's really running against the share, as the result >>> looks exact the same when I ran the test on 2 different shares. >>> >>> Thanks in advance for your help! >> >> Delete the output files and run the test again? If the files are >> created, then you should be able to safely confirm that it is running >> where you think it is running. Fio will prefix any file with the >> --directory= setting. So if you did set it, it should work... >> >> -- >> 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
