Flexible I/O Tester development
 help / color / mirror / Atom feed
From: scameron@beardog.cce.hp.com
To: fio@vger.kernel.org
Cc: scameron@beardog.cce.hp.com
Subject: fio crash when using verify
Date: Tue, 22 Jul 2014 15:59:47 -0500	[thread overview]
Message-ID: <20140722205947.GD14599@beardog.cce.hp.com> (raw)


Hi Jens,

I'm running into a crash with fio today, seems to be easily reproducible.

[root@msablackburn saperf]# fio --version
fio-2.1.11-2-g90811

(top of current git tree.)


[root@msablackburn saperf]# fio ./2drive_sdr_verify.fio
4_KiB_RR_drive_r: (g=0): rw=randwrite, bs=4K-4K/4K-4K/4K-4K, ioengine=libaio, iodepth=170
4_KiB_RR_drive_s: (g=0): rw=randwrite, bs=4K-4K/4K-4K/4K-4K, ioengine=libaio, iodepth=170
fio-2.1.11-2-g90811
Starting 2 threads
fio: io_u.c:1315: __get_io_u: Assertion `io_u->flags & IO_U_F_FREE' failed.a 58m:59s]
Aborted (core dumped)

my fio job file looks like this:

[root@msablackburn saperf]# cat 2drive_sdr_verify.fio
[global]
direct=1
ioengine=libaio
norandommap
randrepeat=0
bs=4096
iodepth=170
#iodepth=96
#numjobs=1
numjobs=1
#numjobs=24
# number_ios=1
# runtime=216000
runtime=3600
time_based=1
group_reporting
thread
gtod_reduce=1
iodepth_batch=4
iodepth_batch_complete=4
cpus_allowed=0-5
cpus_allowed_policy=split
rw=randwrite
verify=crc32c-intel
verify_backlog=1m
do_verify=1
verify_async=6
verify_async_cpus=0-5

[4_KiB_RR_drive_r]
filename=/dev/sdr

[4_KiB_RR_drive_s]
filename=/dev/sds


-- steve


             reply	other threads:[~2014-07-22 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 20:59 scameron [this message]
2014-07-23 10:10 ` fio crash when using verify Jens Axboe
2014-07-23 14:22   ` scameron
2014-07-23 14:23     ` Jens Axboe
2014-07-25 13:09       ` scameron
2014-07-25 13:16         ` Jens Axboe

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=20140722205947.GD14599@beardog.cce.hp.com \
    --to=scameron@beardog.cce.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox