Flexible I/O Tester development
 help / color / mirror / Atom feed
* question on log file command behavior change
@ 2013-08-28 18:48 Roger Sibert
  2013-08-31  4:32 ` Jens Axboe
  0 siblings, 1 reply; 2+ messages in thread
From: Roger Sibert @ 2013-08-28 18:48 UTC (permalink / raw)
  To: FIO

Hello Everyone,

It's been a stretch since I last did something that required logging
logging, that would be going from 2.0 to the latest git clone from
today.

When I tried to use my older fio configuration files with the new fio
it barked about not specifying the write_bw_log name.  The 2.0.x
version used the name from the job so you could have the options
turned on in [global].

Is the change in behavior where you now have to specify the name of
the log (thus requiring it to be in each job) intentional?

fio 2.0.x config
[global]
direct=1
ioengine=libaio
zonesize=256m
zoneskip=768m
randrepeat=1
write_bw_log
write_lat_log
;
[sda-iodepth1-write-bs1k-1]
stonewall
filename=/dev/sda
iodepth=1
rw=write
bs=1k
runtime=45s
time_based
ramp_time=15s

fio 2.1.x git from today
[global]
direct=1
ioengine=libaio
zonesize=256m
zoneskip=768m
randrepeat=1
;
[sdc-iodepth8-write-bs128k-1]
stonewall
filename=/dev/sdc
iodepth=8
rw=write
bs=128k
runtime=45s
time_based
ramp_time=15s
write_bw_log=sdc-iodepth8-write-bs128k-1
write_lat_log=sdc-iodepth8-write-bs128k-1
write_iops_log=sdc-iodepth8-write-bs128k-1


Thanks,
Roger

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-08-31  4:32 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-28 18:48 question on log file command behavior change Roger Sibert
2013-08-31  4:32 ` Jens Axboe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox