Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Danny Kukawka <dkukawka@suse.de>
To: fio@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>
Subject: Re: fio problems
Date: Thu, 05 Apr 2012 11:24:34 +0200	[thread overview]
Message-ID: <4F7D64D2.2040407@suse.de> (raw)
In-Reply-To: <4F7CABC5.7090109@kernel.dk>

[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]

Am 04.04.2012 22:15, schrieb Jens Axboe:
> On 2012-04-04 13:50, Jens Axboe wrote:
>>> 2) fio 2.0.6 and also the current git tends to fail with this error:
> 
>>>    fio 2.0.6
>>>    Starting 1 process
>>>    fio: iolog.c:242: log_io_piece: Assertion `ipo->len == __ipo->len'
>>>    failed.:08m:31s]
> 
>>> It seems that we can prevent it when we use the --size parameter, but we
>>> would like to prevent the usage of the parameter, if possible
> 
>> Strangely, I had two reports of this today. Did a bit of digging, and
>> it's due to this commit:
> 
>> commit c04e4661e4da3b6079f415897e4507cf8e610c54
>> Author: Daniel Ehrenberg <dehrenberg@google.com>
>> Date:   Fri Mar 16 18:54:15 2012 +0100
> 
>>     time_based: Avoid restarting main I/O loop
> 
>> I think what is going on here is that your job is time based, and when
>> we fail getting a new offset, we clear the offset bitmap. But we could
>> have verifies pending at this point, we'd need to prune this out as
>> well.
> 
> Actually, since it happens so rarely, I think the better approach is
> just to ignore it. I've updated fio to reflect that.

Btw. I can suppress the error if I add --size with a high number e.g.
--size=1p.

Danny
-- 
Danny Kukawka
 SUSE LINUX Products GmbH
  Maxfeldstrasse 5, D-90409 Nuremberg, Germany
  GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2012-04-05  9:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  6:39 fio problems Danny Kukawka
2012-04-04 19:50 ` Jens Axboe
2012-04-04 20:15   ` Jens Axboe
2012-04-05  9:24     ` Danny Kukawka [this message]
2012-04-05 14:45       ` Jens Axboe
2012-04-05  8:51   ` Danny Kukawka
2012-04-05 14:42     ` Jens Axboe
2012-04-05 15:30       ` Danny Kukawka
2012-04-05 15:41         ` Jens Axboe
2012-04-05 18:29       ` Usage of group reporting Lucian Grijincu
2012-04-05 22:01         ` 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=4F7D64D2.2040407@suse.de \
    --to=dkukawka@suse.de \
    --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