From: Jens Axboe <axboe@kernel.dk>
To: Grant Grundler <grundler@chromium.org>
Cc: FIO_list <fio@vger.kernel.org>
Subject: Re: [PATCH] Adds check for numberio during verify phase.
Date: Fri, 24 Jan 2014 12:07:32 -0800 [thread overview]
Message-ID: <20140124200732.GI7483@kernel.dk> (raw)
In-Reply-To: <CANEJEGtcapSorcgMYRXiPBpA8sxK+u3VSL8ySyywfJQ29_KABw@mail.gmail.com>
On Fri, Jan 24 2014, Grant Grundler wrote:
> [dropping jcasse since this account was deleted after his internship ended]
>
> On Fri, Jan 24, 2014 at 10:58 AM, Jens Axboe <axboe@kernel.dk> wrote:
> > On Fri, Jan 24 2014, Grant Grundler wrote:
> >> Jens, Ping?
> >> You think you can still integrate the three patches from Juan?
> >
> > I think that would be manageable. But really a new feature (or feature
> > modification) like this should be accompanies by a job file example for
> > it. Care to provide one?
>
> Yes. Do you mind cloning a git repo?
It was big :-)
> Specifically this file is what chromium.org is using:
> https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/client/site_tests/hardware_StorageFio/8k_async_randwrite
>
> The git repo is hosted here:
> https://chromium.googlesource.com/chromiumos/third_party/autotest/
>
> Use git clone to pull the entire repo:
> git clone https://chromium.googlesource.com/chromiumos/third_party/autotest
>
>
> BTW, Verification is failing on the 1m_stress control file...working
> on that now:
> https://code.google.com/p/chromium/issues/detail?id=337651
>
> I suspect it's a problem of the control file though since we are
> getting this warning:
> "Multiple writers may overwrite blocks that belong to other jobs.
> This can cause verification failures."
Yes, with 8 jobs going, they are going to be stomping on each others
blocks potentially.
I queued up the 3 patches, but I killed the --verify-only command line
switch. Seems unneeded, might as well just use the job option for that.
--
Jens Axboe
next prev parent reply other threads:[~2014-01-24 20:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 21:06 [PATCH] Adds check for numberio during verify phase Juan Casse
2013-09-17 21:06 ` [PATCH V3] Adds verify_only option Juan Casse
2014-01-24 18:34 ` Grant Grundler
2013-09-17 21:06 ` [PATCH] Adds check for rand_seed during verify phase Juan Casse
2014-01-24 18:35 ` Grant Grundler
2014-01-24 18:34 ` [PATCH] Adds check for numberio " Grant Grundler
2014-01-24 18:58 ` Jens Axboe
2014-01-24 19:22 ` Grant Grundler
2014-01-24 20:07 ` Jens Axboe [this message]
2014-01-24 20:48 ` Grant Grundler
2014-01-24 21:19 ` Jens Axboe
2014-01-24 22:56 ` Grant Grundler
2014-01-24 23:17 ` Jens Axboe
2014-01-24 20:27 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2013-09-06 3:10 Juan Casse
2013-09-16 22:24 ` Juan Casse
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=20140124200732.GI7483@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=grundler@chromium.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 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.