From: Rebecca Cran <rebecca@bluestop.org>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: fio <fio@vger.kernel.org>,
Rob Scheepens <rob.scheepens@nutanix.com>,
David Knierim <knierim@nutanix.com>
Subject: Re: Windows: FIO randomly hangs using attached script
Date: Tue, 6 Mar 2018 13:01:46 -0700 [thread overview]
Message-ID: <9cf7d62a-5c4a-737a-d119-13763fb42c72@bluestop.org> (raw)
In-Reply-To: <CALjAwxjoTtRp1jVhfKMTcbn6wnmEmmCsjkpO7CkBgF5zj4B3Bg@mail.gmail.com>
On 3/6/2018 9:35 AM, Sitsofe Wheeler wrote:
>
> I tried out the python script but it seemed to be complaining about a
> whitespace issue. After fixing that up it's unclear exactly what fio
> command lines it runs. I think for others to dig in we'd need
> something less fiddly like the raw fio command lines that generate the
> hang. Is there any chance the mystery user could join the mailing list
> so they can answer questions directly? Ideally we'd need a job that
> works on files within a filesystem and ideally nice small files so it
> could go into an AppVeyor job...
>
I've CC'd Rob and David.
You can find the FIO command lines used by running the script in verbose
mode: it lists them all at the start, then steps through them one by
one. Unfortunately nobody's had any luck in narrowing down a single run
that causes the hang.
I forgot to say that the problem has been seen on FIO 3.1 - I never got
around to trying it on version 3.5, which is now on
https://bluestop.org/fio .
--
Rebecca
next prev parent reply other threads:[~2018-03-06 20:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 1:23 Windows: FIO randomly hangs using attached script Rebecca Cran
2018-03-06 16:35 ` Sitsofe Wheeler
2018-03-06 20:01 ` Rebecca Cran [this message]
2018-03-07 6:00 ` Sitsofe Wheeler
2018-03-07 15:33 ` David Knierim
2018-03-07 15:39 ` Rob Scheepens
2018-03-07 16:01 ` Sitsofe Wheeler
2018-03-07 16:03 ` Rebecca Cran
2018-03-07 16:05 ` Rob Scheepens
2018-03-07 16:09 ` Rebecca Cran
2018-03-08 10:51 ` Rob Scheepens
2018-03-08 12:28 ` Sitsofe Wheeler
2018-03-08 12:39 ` Rob Scheepens
2018-03-08 14:35 ` Rob Scheepens
2018-03-08 14:38 ` Rob Scheepens
2018-03-08 15:15 ` Sitsofe Wheeler
2018-03-08 15:13 ` Sitsofe Wheeler
2018-03-08 15:45 ` Rob Scheepens
2018-03-08 15:47 ` Sitsofe Wheeler
2018-03-08 15:46 ` Sitsofe Wheeler
2018-03-08 15:59 ` Sitsofe Wheeler
2018-03-08 16:18 ` Jens Axboe
2018-03-09 14:40 ` Sitsofe Wheeler
2018-03-09 14:55 ` Jens Axboe
2018-03-16 8:13 ` Sitsofe Wheeler
2018-05-01 14:41 ` Rob Scheepens
2018-05-01 14:42 ` Jens Axboe
2018-05-01 14:58 ` Sitsofe Wheeler
2018-03-08 22:44 ` Sitsofe Wheeler
2018-03-06 21:53 ` Jens Axboe
2018-03-06 22:35 ` Rebecca Cran
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=9cf7d62a-5c4a-737a-d119-13763fb42c72@bluestop.org \
--to=rebecca@bluestop.org \
--cc=fio@vger.kernel.org \
--cc=knierim@nutanix.com \
--cc=rob.scheepens@nutanix.com \
--cc=sitsofe@gmail.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.