Where log_offset description is given It will be best to have one liner saying if log_avg_msec parameter is used offset wont be logged. This will make it very clear. On Sat, Mar 10, 2018 at 1:18 AM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: > Hi, > > Glad to hear you found the cause. Nonetheless, do you think the > documentation needs changing and if so how? > > On 10 March 2018 at 08:07, abhishek koundal <akoundal@xxxxxxxxx> wrote: >> yes you are correct. thanks for the information, i can see the offset >> w/o the log_avg_msec. >> appreciate your prompt support. >> >> On Fri, Mar 9, 2018 at 9:48 PM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: >>> On 9 March 2018 at 22:59, abhishek koundal <akoundal@xxxxxxxxx> wrote: >>>> >>>> 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% --filename=/dev/nvme0n1 >>>> --runtime=10 --write_iops_log=wr.log --log_avg_msec=1000 >>>> --log_offset=1 >>>> >>>> Still seeing the issue. >>> >>> log_avg_msec=1000 tries to average values seen every second which >>> means some values will become nonsense when it's enabled. There's a >>> warning at the end of the "Log File Formats" section of the HOWTO >>> (http://fio.readthedocs.io/en/latest/fio_doc.html#log-file-formats ) >>> but perhaps it needs to be moved elsewhere - would it have been better >>> under the log_avg_msec section of the HOWTO >>> (http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-log-avg-msec >>> )? > > -- > 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
