All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: George T Seese <george.t.seese@seagate.com>, fio@vger.kernel.org
Subject: Re: Log Bug with fio-2.1.14 and Higher Causing fio Jobs to Time Out
Date: Mon, 12 Jan 2015 16:50:22 -0700	[thread overview]
Message-ID: <54B45DBE.4000705@kernel.dk> (raw)
In-Reply-To: <CAFCBNRFzOw4rVnWpHWN=FfdhDYePKwP9xo7vWdKTPR+LSpyZwQ@mail.gmail.com>

On 01/09/2015 09:04 AM, George T Seese wrote:
> fio team,
> 
> I've found a bug that results in fio hanging at the end of a workload
> involving log generation, in this case specific to latency log
> generation. The bug appears in version 2.1.14, 2.2.4, and possibly
> others. I have tested these scripts with 2.0.9 and they work. Slightly
> different scripts work on 2.0.14 as well.
> 
> Error message and script file are copy-pasted below. The job that
> times out is not always the same job but, usually at least one does
> time out, it's worse with more targets.
> 
> fio: pid=37182, got signal=11
> fio: job '/dev/sdc' hasn't exited in 60 seconds, it appears to be
> stuck. Doing forceful exit of this job.
> 
> [global]
> bs=4k
> runtime=1800
> rw=randread
> ;thread=1
> direct=1
> ioengine=libaio
> ;offset=0
> ;randommap=1
> ;time_based=1
> bwavgtime=5000
> ;write_lat_log
> ;stonewall=1
> iodepth=1
> 
> ;TargetDriveMarker
> [/dev/sdc]
> filename=/dev/sdc
> write_lat_log=sdc
> 
> [/dev/sdd]
> filename=/dev/sdd
> write_lat_log=sdd

Thanks, I'll take a look at this.

-- 
Jens Axboe



  reply	other threads:[~2015-01-12 23:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 16:04 Log Bug with fio-2.1.14 and Higher Causing fio Jobs to Time Out George T Seese
2015-01-12 23:50 ` Jens Axboe [this message]
2015-01-14  2:49   ` Jens Axboe
2015-01-14  4:02     ` 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=54B45DBE.4000705@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=george.t.seese@seagate.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.