From: Jens Axboe <axboe@kernel.dk>
To: "Robin P. Blanchard" <robin@coraid.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: regression since 2.1.3 (solaris/zfs)
Date: Mon, 03 Mar 2014 08:25:39 -0700 [thread overview]
Message-ID: <53149EF3.7020005@kernel.dk> (raw)
In-Reply-To: <1E602C14-0C00-4258-94C2-8F16A56C509D@coraid.com>
On 03/02/2014 07:59 AM, Robin P. Blanchard wrote:
> My config file has direct=0, which until 2.1.4 worked as expected.
> Things seem to regress since.
>
> I apologize in advance if this has already been reported. Please
> let me know what I can do to further help (truss/debug).
This isn't a known issue, so thanks for reporting it. The easiest way to
debug this is to git bisect it. Looks like you are running from the tar
balls, but I assume you have git installed? I'm assuming fio-2.1.3
worked for you - if not, just replace fio-2.1.3 in the below with
whatever latest version did work. If you do, the cheat sheet is
something ala:
$ git clone git://git.kernel.dk/fio
$ cd fio; make
$ git bisect start
$ git bisect good fio-2.1.3
$ git bisect bad fio-2.1.4
This starts the bisect series, now do:
$ make clean; make
and re-run your direct=0 job file. If it worked, then you do
$ git bisect good
and if not, you do git bisect bad instead. This gets you a new point in
the tree to test, so repeat the make clean; make and re-run the test.
Keep doing this good/bad iteration until fio tells you what commit broke
the test for you. Then send those results here!
--
Jens Axboe
next prev parent reply other threads:[~2014-03-03 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 14:59 regression since 2.1.3 (solaris/zfs) Robin P. Blanchard
2014-03-03 15:25 ` Jens Axboe [this message]
2014-03-05 16:11 ` Robin P. Blanchard
2014-03-05 16:18 ` Jens Axboe
2014-03-05 16:27 ` Robin P. Blanchard
2014-03-05 17:06 ` Jens Axboe
2014-03-05 20:39 ` Robin P. Blanchard
2014-03-05 21:05 ` Jens Axboe
2014-03-05 21:12 ` Robin P. Blanchard
2014-03-05 21:14 ` 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=53149EF3.7020005@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=robin@coraid.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.