All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben England <bengland@redhat.com>
To: fio@vger.kernel.org
Cc: Tim Wilkinson <twilkins@redhat.com>
Subject: assert failing with latency log
Date: Tue, 24 May 2016 17:40:10 -0400 (EDT)	[thread overview]
Message-ID: <897324962.65623516.1464126010451.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <632274204.65621860.1464125206824.JavaMail.zimbra@redhat.com>

If I run this fio jobfile with absolute latest upstream code:

[global]
directory=/var/tmp

[randreads]
direct=1
rate_iops=1000
size=512m
ioengine=sync 
bs=4k 
rw=randread
filename=ben.dd 
runtime=30
write_lat_log=foo

It fails with 

fio: stat.c:1988: get_cur_log: Assertion `iolog->pending->nr_samples < iolog->pending->max_samples' failed.

But if I take out the "write_lat_log=foo" line, it succeeds.  The assertion seems to be in the code path for latency logs, right?  Anyone else seen this?



       reply	other threads:[~2016-05-24 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <632274204.65621860.1464125206824.JavaMail.zimbra@redhat.com>
2016-05-24 21:40 ` Ben England [this message]
2016-05-25  0:41   ` assert failing with latency log Jens Axboe
2016-05-25  2:02     ` Ben England

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=897324962.65623516.1464126010451.JavaMail.zimbra@redhat.com \
    --to=bengland@redhat.com \
    --cc=fio@vger.kernel.org \
    --cc=twilkins@redhat.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.