From: Saeed <ionictea@gmail.com>
To: fio@vger.kernel.org
Subject: Re: multiple entries for each second for bw/iop/xlat log files
Date: Mon, 22 Aug 2016 15:47:58 -0500 [thread overview]
Message-ID: <npfodt$uqa$1@blaine.gmane.org> (raw)
In-Reply-To: caf6faa7-9584-724c-2c5b-a6fb1a2af441@kernel.dk
I'm still getting the same problem where there seems to be duplicate
time interval entries and no data for the iops log using the latest git:
479999, 1, 0, 4096
479999, 1, 0, 4096
479999, 1, 0, 4096
479999, 1, 0, 4096
479999, 1, 0, 4096
479999, 1, 0, 4096
479999, 1, 0, 4096
480000, 1, 0, 4096
I do see the following errors during the configure process but not sure
if its related:
/tmp/fio-conf--8430-.c:2:2: error: #error __ANDROID__ not defined
#error __ANDROID__ not defined
/tmp/fio-conf--8430-.c:2:2: error: #error __i386__ not defined
#error __i386__ not defined
/tmp/fio-conf--8430-.c:5:3: error: size of unnamed array is negative
collect2: error: ld returned 1 exit status
/tmp/fio-conf--8430-.c:2:24: fatal error: sys/asynch.h: No such file or
directory
/tmp/fio-conf--8430-.c:2:29: fatal error: infiniband/arch.h: No such
file or directory
/tmp/fio-conf--8430-.c:2:27: fatal error: rdma/rdma_cma.h: No such file
or directory
/tmp/fio-conf--8430-.c:5:24: error: 'CLOCK_MONOTONIC_PRECISE'
undeclared (first use in this function)
/tmp/fio-conf--8430-.c:5:22: error: storage size of 'me' isn't known
/tmp/fio-conf--8430-.c:6:19: error: 'EXT4_IOC_MOVE_EXT' undeclared
(first use in this function)
/tmp/fio-conf--8430-.c:1:19: fatal error: guasi.h: No such file or directory
/tmp/fio-conf--8430-.c:1:32: fatal error: nvm/nvm_primitives.h: No such
file or directory
/tmp/fio-conf--8430-.c:1:18: fatal error: numa.h: No such file or directory
collect2: error: ld returned 1 exit status
collect2: error: ld returned 1 exit status
/tmp/fio-conf--8430-.c:1:24: fatal error: rbd/librbd.h: No such file or
directory
/tmp/fio-conf--8430-.c:1:24: fatal error: rbd/librbd.h: No such file or
directory
/tmp/fio-conf--8430-.c:1:32: fatal error: glusterfs/api/glfs.h: No such
file or directory
/tmp/fio-conf--8430-.c:7: Error: unknown pseudo-op: `.machine'
/tmp/fio-conf--8430-.c:8: Error: unknown pseudo-op: `.machine'
/tmp/fio-conf--8430-.c:9: Error: no such instruction: `stfle %rcx'
/tmp/fio-conf--8430-.c:10: Error: unknown pseudo-op: `.machine'
/tmp/fio-conf--8430-.c:6:17: error: storage size of 'st' isn't known
/tmp/fio-conf--8430-.c:7:26: error: 'MNT_NOWAIT' undeclared (first use
in this function)
On 2016-08-22 17:33:13 +0000, Jens Axboe said:
> On 08/22/2016 10:37 AM, Saeed wrote:
>> Why are there multiple entries for each interval / second in the fio log
>> generated?
>>
>> 1, 585142, 1, 4096
>> 1, 4096000, 1, 4096
>> 1, 4096000, 1, 4096
>> 1, 0, 1, 4096
>> 1, 0, 1, 4096
>> 1, 4096000, 1, 4096
>> 1, 0, 1, 4096
>> 1, 0, 1, 4096
>> 1, 4096000, 1, 4096
>> 1, 0, 1, 4096
>> 2, 4096000, 1, 4096
>> 2, 4096000, 1, 4096
>> 2, 4096000, 1, 4096
>> 2, 0, 1, 4096
>> 2, 4096000, 1, 4096
>> 2, 4096000, 1, 4096
>> 2, 4096000, 1, 4096
>> 2, 0, 1, 4096
>> 2, 0, 1, 4096
>> 2, 0, 1, 4096
>
> Ditto for this one, try current -git.
next prev parent reply other threads:[~2016-08-22 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 16:37 multiple entries for each second for bw/iop/xlat log files Saeed
2016-08-22 17:33 ` Jens Axboe
2016-08-22 20:47 ` Saeed [this message]
2016-08-22 20:58 ` Karl Cronburg
2016-08-22 21:17 ` Saeed
2016-08-23 1:05 ` Saeed
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='npfodt$uqa$1@blaine.gmane.org' \
--to=ionictea@gmail.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.