Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Matt Freel <matt.freel@broadcom.com>
To: fio@vger.kernel.org
Subject: Proper way to shut down FIO in Linux
Date: Tue, 13 Mar 2018 12:56:10 -0600	[thread overview]
Message-ID: <8d5a5fe209774d24b9df39cf6a226dbb@mail.gmail.com> (raw)

I'm using FIO to run IOs to a number of block devices.  I'm looking for
the proper way to shut down all the threads that are spawned.

I'm doing the following:

/usr/bin/pkill --signal INT fio

Most of the time this works fine, but I do have cases where some of the
FIO processes remain open.  Eventually I get a 300s timeout and then
they're killed.

A couple questions:

1.	When these threads have to be ungracefully killed, do the results
still get counted in the output file?
a.	I'm using JSON output file
2.	Is there a better way I should be killing all the threads?

             reply	other threads:[~2018-03-13 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 18:56 Matt Freel [this message]
2018-03-14  6:46 ` Proper way to shut down FIO in Linux Erwan Velu
2018-03-14 15:07   ` Matt Freel
2018-03-17  6:34     ` Sitsofe Wheeler
2018-03-21 14:36 ` Jens Axboe
2018-03-21 14:39   ` Matt Freel

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=8d5a5fe209774d24b9df39cf6a226dbb@mail.gmail.com \
    --to=matt.freel@broadcom.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