From: Jens Axboe <axboe@kernel.dk>
To: "Hinson, Roger" <Roger_Hinson@intuit.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Block size of zero in log files
Date: Wed, 25 Jun 2014 09:20:58 -0600 [thread overview]
Message-ID: <53AAE8DA.90002@kernel.dk> (raw)
In-Reply-To: <ab186420ecb140c887b85f36fcdde766@BLUPR02MB453.namprd02.prod.outlook.com>
On 2014-06-24 18:33, Hinson, Roger wrote:
> Hi,
>
> I'm new to using FIO. I'm using FIO 2.1.10, although I had the same problem with FIO 2.1.7. The log files are not listing the blocksize. I looked around and can't find anything obvious that I'm doing wrong, although I see posts with it working for people. Has anyone seen and solved this?
>
> Here is a snippet from my FIO config file.
>
> [global]
> thread
> group_reporting=1
> direct=1
> norandommap=0
> randrepeat=0
> refill_buffers
> buffer_compress_percentage=0
> ioengine=libaio
> #filename=/dev/dm-0:/dev/dm-1:/dev/dm-2:/dev/dm-3:/dev/dm-4:/dev/dm-5
>
> log_avg_msec=1000
>
> [128kB_SeqWr_dm0_1stPass]
> write_bw_log=128kB_SeqWr_dm0_1stPass
> write_lat_log=128kB_SeqWr_dm0_1stPass
> write_iops_log=128kB_SeqWr_dm0_1stPass
> filename=/dev/dm-0
> bs=128k
> rw=write
> numjobs=1
> iodepth=8
>
> [128kB_SeqWr_dm1_1stPass]
> write_bw_log=128kB_SeqWr_dm1_1stPass
> write_lat_log=128kB_SeqWr_dm1_1stPass
> write_iops_log=128kB_SeqWr_dm1_1stPass
> filename=/dev/dm-1
> bs=128k
> rw=write
> numjobs=1
> iodepth=8
>
> and a snippet of a log file
>
> tail -5 128kB_SeqWr_dm0_1stPass_bw.log
>
> 10767282, 171175, 1, 0
> 10768286, 167055, 1, 0
> 10769288, 172508, 1, 0
> 10770292, 170629, 1, 0
> 10770926, 174754, 1, 0
When you are looking over an averaged window (log_avg_msec), you no
longer have a 1:1 between log entry and IO. So you lose the blocksize
information.
--
Jens Axboe
prev parent reply other threads:[~2014-06-25 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 0:33 Block size of zero in log files Hinson, Roger
2014-06-25 15:20 ` Jens Axboe [this message]
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=53AAE8DA.90002@kernel.dk \
--to=axboe@kernel.dk \
--cc=Roger_Hinson@intuit.com \
--cc=fio@vger.kernel.org \
/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.