From: Jens Axboe <axboe@kernel.dk>
To: Jeff Furlong <jeff.furlong@hgst.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio bw and iops logs broken
Date: Mon, 6 Jun 2016 21:08:15 -0600 [thread overview]
Message-ID: <57563A9F.8090906@kernel.dk> (raw)
In-Reply-To: <BN3PR0401MB14570C741575E615FE199142F75C0@BN3PR0401MB1457.namprd04.prod.outlook.com>
On 06/06/2016 04:07 PM, Jeff Furlong wrote:
> Hi All,
> Somewhere between fio-2.11 and fio-2.11-14-gf031 the bw and iops logs no longer get written.
>
> # fio --name=test_job --ioengine=libaio --direct=1 --rw=write --iodepth=32 --size=100% --numjobs=1 --bs=1m --filename=/dev/nvme0n1 --group_reporting --write_bw_log=test_job --write_iops_log=test_job --write_lat_log=test_job --log_avg_msec=1000 --disable_lat=0 --disable_clat=0 --disable_slat=0 --runtime=10s --ramp_time=5s --output=test_job
>
> # ls -l
> -rw-r--r-- 1 root root 1537 Jun 6 15:01 test_job
> -rw-r--r-- 1 root root 0 Jun 6 15:01 test_job_bw.1.log
> -rw-r--r-- 1 root root 199 Jun 6 15:01 test_job_clat.1.log
> -rw-r--r-- 1 root root 0 Jun 6 15:01 test_job_iops.1.log
> -rw-r--r-- 1 root root 200 Jun 6 15:01 test_job_lat.1.log
> -rw-r--r-- 1 root root 254 Jun 6 15:01 test_job_slat.1.log
>
> See above file sizes of zero for the bw and iops logs. However, lat/slat/clat are written. Thoughts on which recent commit broke the functionality? Thanks.
I'll take a look.
--
Jens Axboe
next prev parent reply other threads:[~2016-06-07 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 22:07 fio bw and iops logs broken Jeff Furlong
2016-06-07 3:08 ` Jens Axboe [this message]
2016-06-07 3:25 ` Jens Axboe
2016-06-07 16:50 ` Jeff Furlong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57563A9F.8090906@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=jeff.furlong@hgst.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.