fio --name=global --time_based --size=100% --filename=/dev/nvme0n1 --runtime=10 --write_iops_log=wr.log --log_avg_msec=1000 --log_offset=1 Still seeing the issue. On Fri, Mar 9, 2018 at 1:52 PM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: > Hi, > > On 9 March 2018 at 20:11, abhishek koundal <akoundal@xxxxxxxxx> wrote: >> All, >> Can someone please confirm if my usage is correct as earlier the >> offset used to be logged by using the log_offset=1 in the files. >> I am using FIO3.5. >> >> fio --name=global --time_based --size=100% --direct=1 --norandommap >> --randrepeat=0 --buffered=0 --refill_buffers --name=job >> --ioengine=libaio --group_reporting --filename=/dev/nvme0n1 >> --numjobs=1 --iodepth=128 --bs=128k --rw=rw --rwmixread=70 >> --runtime=10800 --write_iops_log=wr.log -write_lat_log=wr.clat.log >> --log_avg_msec=1000 --log_offset=1 > > To help us out a bit can you cut back as many options as possible? > Ideally you should try to get to the point where you have the minimum > number of options that still show the problem (i.e. to the point where > you can't remove any one option and still have the problem happen)? > For example I bet you can remove "--direct=1 --norandommap" and still > have the problem you describe happen. It just makes it easier to > investigate when there are less places to look... > > -- > Sitsofe | http://sucs.org/~sits/ -- Life is too short for silly things so invest your time in some productive outputs!! -- 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
