Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Carl Zwanzig <cpz@coraid.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Fio ignoring runtime after an error?
Date: Wed, 17 Apr 2013 08:12:36 +0200	[thread overview]
Message-ID: <20130417061236.GD4816@kernel.dk> (raw)
In-Reply-To: <A7A1D348E34E024BBC74480FB93A2EAB026DFC@DAGN05A-E6.exg6.exghost.com>

On Tue, Apr 16 2013, Carl Zwanzig wrote:
> Hello,
> 
> I think I've run across a case where, during a time-limited test, a soft error occurred on the device and fio continued to run -way- past (overnight) the time limit.
> 
> The rough scenario is:
> fio test - ok
> fio test - ok
> fio test - starts
>   soft error
> fio never ends (and is still pushing traffic as reported by the disk system)
> 
> I haven't had a chance to dive into the code yet (fio 2.0.14, linux 2.6.32-279.14.1.el6.x86_64), but can anyone think of a reason why this would happen?
> 
> The command line looks like:
> fio --name='raid0;16;randread;8;16' --rw=randread --filename=/dev/ethdrv/e107.1 --iodepth=16 --bs=8k --rwmixread=70 --norandommap --group_reporting --time_based --minimal --direct=1 --fill_device=1 --ioengine=libaio --ramp_time=5 --runtime=35 --randrepeat=0
> 
> Hopefully, I'll get the clue to inject an error into the disk system and run this down, but that'll take time I don't really have.

What kind of error? For fill_device=1, fio will clear ENOSPC, but should
not clear other errors. Apart from that, there should not be any
interactions between errors and runtime/time_based.

-- 
Jens Axboe


      parent reply	other threads:[~2013-04-17  6:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 17:54 Fio ignoring runtime after an error? Carl Zwanzig
2013-04-16 22:12 ` Greg Freemyer
2013-04-17  6:12 ` Jens Axboe [this message]

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=20130417061236.GD4816@kernel.dk \
    --to=jaxboe@fusionio.com \
    --cc=cpz@coraid.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