All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: flash yan <flashyan83@gmail.com>, fio@vger.kernel.org
Subject: Re: Linux OS killed fio process because fio invoked oom_killer
Date: Tue, 22 Mar 2016 10:30:30 -0600	[thread overview]
Message-ID: <56F17326.3000908@kernel.dk> (raw)
In-Reply-To: <CADvrUP8gH3S-fLnHU4QXJLO87YzUge8MxKt3WdffN+9uiVpH3w@mail.gmail.com>

On 03/22/2016 08:06 AM, flash yan wrote:
> Hi all,
>
> I have run fio-2.7 to test iscsi device, one unusual issue happened.
> If I set the io_size to 4096, queue_depth to 16 ,rw to randwrite and
> run_time to 3000,
> the fio would invoke oom_killer and the Linux OS would kill the fio process.
> The machine have about 11 GB memory and I have tried the machine with
> 23GB, the issue also happened.
> I think fio have problem when dealing with 4KB io_size then used too
> many memory.

When did this happen - shortly after the job is started, or long after? 
How big is the iscsi device? Did you have verify= options enabled?

-- 
Jens Axboe



  reply	other threads:[~2016-03-22 16:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 14:06 Linux OS killed fio process because fio invoked oom_killer flash yan
2016-03-22 16:30 ` Jens Axboe [this message]
2016-03-22 23:12   ` flash yan
2016-03-23  0:42     ` Jens Axboe
2016-03-23 15:10       ` flash yan
2016-03-23 19:29         ` Jeff Furlong
2016-03-23 22:51           ` flash yan
2016-03-23 23:32             ` Jeff Furlong
2016-03-24 12:50               ` flash yan
2016-03-24 14:06                 ` Jens Axboe
2016-03-24 19:39                   ` Jens Axboe
2016-03-24 23:33                     ` flash yan
2016-03-25 15:03                     ` flash yan
2016-03-25 15:10                       ` Jens Axboe
2016-03-27 12:00                         ` flash yan

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=56F17326.3000908@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=flashyan83@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.