I eventually want to specify a job on the command line that includes collecting latency/bandwidth/iops logs. I have a command/job script combination that makes latency logs in 1.38 and doesn't in 1.39. I fail to get latency logs for a fair sample of fio versions from 1.39 to 2.07. I discovered this in attempting to figure out where the behavior changed. cat ./run # /loaner/semery/fio/fio-1.39/fio --output test.small.loaner --latency-log --bandwidth-log --alloc-size=4096 test.small cat test.small # [global] bs=2m ioengine=libaio iodepth=1 size=1g direct=1 runtime=1200 directory=/loaner/semery/fio/latencylogs group_reporting [seq-read] rw=read numjobs=2 [seq-write] new_group rw=write numjobs=1 When run uses fio-1.38 I get the following: [semery@lou2-mov4 latencylogs]$ ./run [semery@lou2-mov4 latencylogs]$ ls run seq-write.3.0 test.putgetstorm.iod4.loaner seq-read.1.0 seq-write_clat.log test.small seq-read.2.0 seq-write_slat.log test.small.loaner With fio-1.39 I get: [semery@lou2-mov4 latencylogs]$ ls run seq-write.3.0 test.putgetstorm.iod4.loaner seq-read.1.0 test.putgetstorm test.small seq-read.2.0 test.putgetstorm.iod4 test.small.loaner I grovelled through a diff -r of 1.38 and 1.39 and the significant looking difference is this: diff -r fio-1.38/init.c fio-1.39/init.c 884,886d883 < def_thread.o.write_bw_log = write_bw_log; < def_thread.o.write_lat_log = write_lat_log; < Have latency logs, et. al. been deprecated? Is there a new/better way to get them? Scott Emery emery@xxxxxxx -- 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
