All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Jeff Furlong <jeff.furlong@hgst.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio signal 11
Date: Fri, 10 Jun 2016 08:17:13 +0100	[thread overview]
Message-ID: <CALjAwxhv8pCLJe0uT6PX1r7g4Mu=d8gA19VUFu0pUE9LkHTkrw@mail.gmail.com> (raw)
In-Reply-To: <BN3PR0401MB1457415455A5B0CEFB84447DF75F0@BN3PR0401MB1457.namprd04.prod.outlook.com>

On 9 June 2016 at 22:58, Jeff Furlong <jeff.furlong@hgst.com> wrote:
>
> Using the latest version from git, I am getting a signal 11 error when running some workloads.  It may be that workloads fail when we wrap around the device capacity (e.g. runtime and time_based).  See below example parameters:
>
> # fio --name=test_job --ioengine=libaio --direct=1 --rw=write --iodepth=32 --size=100% --numjobs=1 --bs=1m --filename=/dev/nvme0n1 --group_reporting --write_bw_log=test_job --write_iops_log=test_job --write_lat_log=test_job --log_avg_msec=1000 --disable_lat=0 --disable_clat=0 --disable_slat=0 --runtime=1500s --time_based --ramp_time=5s --output=test_job
>
> fio-2.11-17-ga275
> Starting 1 process
> fio: pid=145763, got signal=11

Could you run fio under gdb (
gdb ./fio
run --name=test_job --ioengine=libaio etc.
)

and when it crashes get a backtrace with
thread apply all bt
?

-- 
Sitsofe | http://sucs.org/~sits/

  reply	other threads:[~2016-06-10  7:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 21:58 fio signal 11 Jeff Furlong
2016-06-10  7:17 ` Sitsofe Wheeler [this message]
2016-06-10 18:42   ` Jeff Furlong
2016-06-12  2:56     ` Jens Axboe
2016-06-12  3:30       ` Jens Axboe
2016-06-13 17:58         ` Jeff Furlong
2016-06-13 18:01           ` Jens Axboe
2016-06-13 18:04             ` Jeff Furlong
2016-06-13 19:21               ` Jeff Furlong
2016-06-13 19:23                 ` Jens Axboe
2016-06-13 19:34                   ` Jens Axboe
2016-06-13 20:55                     ` Jeff Furlong
2016-06-13 21:23                       ` Jens Axboe
2016-06-15 14:45         ` Jan Kara
2016-06-16  7:06           ` Jens Axboe
2016-07-20  5:08             ` Jan Kara
2016-07-25 15:21               ` Jens Axboe
2016-07-26  8:43                 ` Jan Kara
2016-07-26 14:17                   ` Jens Axboe
2016-07-26 18:33                     ` Jeff Furlong
2016-07-26 18:35                       ` Jens Axboe
2016-08-01 22:57                         ` Jeff Furlong
2016-08-02 21:03                           ` Jens Axboe
2016-08-03 14:55                           ` Jens Axboe
2016-08-03 15:02                             ` Jeff Furlong
2016-08-03 15:03                               ` Jens Axboe
2016-08-03 15:14                                 ` Jens Axboe
2016-08-03 15:29                                   ` Jeff Furlong

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='CALjAwxhv8pCLJe0uT6PX1r7g4Mu=d8gA19VUFu0pUE9LkHTkrw@mail.gmail.com' \
    --to=sitsofe@gmail.com \
    --cc=fio@vger.kernel.org \
    --cc=jeff.furlong@hgst.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.