From: scameron@beardog.cce.hp.com
To: Jens Axboe <axboe@kernel.dk>
Cc: fio@vger.kernel.org, scameron@beardog.cce.hp.com
Subject: Re: fio crash when using verify
Date: Fri, 25 Jul 2014 08:09:11 -0500 [thread overview]
Message-ID: <20140725130911.GL14599@beardog.cce.hp.com> (raw)
In-Reply-To: <53CFC571.1090709@kernel.dk>
On Wed, Jul 23, 2014 at 04:23:45PM +0200, Jens Axboe wrote:
> On 2014-07-23 16:22, scameron@beardog.cce.hp.com wrote:
> >On Wed, Jul 23, 2014 at 12:10:09PM +0200, Jens Axboe wrote:
> >>On 2014-07-22 22:59, scameron@beardog.cce.hp.com wrote:
> >>>
> >>>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)
> >>
> >>Looks like there's a long standing race in the async verification. Does
> >>this patch fix it for you?
> >
> >So far so good. Been running for about 30 minutes now when previously it
> >would crash within a minute or two.
>
> Good, that's a lot better... The fix has been committed, btw, that's how
> much confidence I have in my fixes ;-)
>
> Let me know how it goes when it has run longer.
Seems to be holding up. I have now run this overnight a couple times without issue.
-- steve
next prev parent reply other threads:[~2014-07-25 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 20:59 fio crash when using verify scameron
2014-07-23 10:10 ` Jens Axboe
2014-07-23 14:22 ` scameron
2014-07-23 14:23 ` Jens Axboe
2014-07-25 13:09 ` scameron [this message]
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=20140725130911.GL14599@beardog.cce.hp.com \
--to=scameron@beardog.cce.hp.com \
--cc=axboe@kernel.dk \
--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