From: Sitsofe Wheeler <sitsofe@gmail.com>
To: "آرش خاوری راد" <arash.khavary@gmail.com>
Cc: fio <fio@vger.kernel.org>
Subject: Re: get err 5
Date: Wed, 1 Aug 2018 07:33:55 +0100 [thread overview]
Message-ID: <CALjAwxh05QQRb1zLe_zkdbymHnjHOh-qaTPrXTwbMNJK4wXSKg@mail.gmail.com> (raw)
In-Reply-To: <CAKTzs3R0S8q=tCkNZ99xqpJpjcAjDCphdSV_GvBbGKRA3GWOUw@mail.gmail.com>
On 1 August 2018 at 06:31, آرش خاوری راد <arash.khavary@gmail.com> wrote:
> Hi i got this error when test FIO sequential write every time, in sequential
> read, random read, random write not got this.
>
> my Linux distro is CentOS Linux release 7.5.1804 (Core)
> and my kernel version is 3.10.0-327.10.1.el7.x86_64
>
> My output is:
>
> job1: (g=0): rw=write, bs=(R) 4096KiB-4096KiB, (W) 4096KiB-4096KiB, (T)
> 4096KiB-4096KiB, ioengine=libaio, iodepth=16
[snip]
>
> My parameter is :
>
>
> [global]
> readwrite=write
> blocksize=4m
> direct=1
[snip]
>
> [job1]
> numjobs=3
> filename=/dev/sdb
>
>
> [job2]
> numjobs=2
> filename=/dev/sdc
>
>
> [job3]
> numjobs=3
> filename=/dev/sdd
>
>
> [job4]
> numjobs=3
> filename=/dev/sde
>
>
> [job5]
> numjobs=2
> filename=/dev/sdf
>
>
> [job6]
> numjobs=3
> filename=/dev/sdg
[snip]
> Why get err 5?
> thanks
So you have 6 separate jobs and the jobs specify numjobs. If we add
all the numjobs together we get 16. You specify a giant blocksize (4
megabytes) which is strangely big unless you are doing unless you're
doing extreme NVMe testing. You also specify an iodepth of 16. So 16 *
16 * 4 = 1024 megabytes of I/O buffers - are you sure you're not
causing yourself to hit memory issues?
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2018-08-01 8:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 5:31 get err 5 آرش خاوری راد
2018-08-01 6:33 ` Sitsofe Wheeler [this message]
2018-08-01 6:39 ` Alireza Haghdoost
2018-08-01 6:51 ` Sitsofe Wheeler
2018-08-01 9:18 ` Alireza Haghdoost
[not found] ` <CAKTzs3TsUT4y7X9gEAExwg3yVLL5eLrYS0S9tZtgO7P75ZV9Bw@mail.gmail.com>
2018-08-07 5:28 ` Sitsofe Wheeler
2018-08-07 6:17 ` آرش خاوری راد
2018-08-07 9:26 ` آرش خاوری راد
2018-08-07 14:42 ` Michael Green
2018-08-07 16:30 ` آرش خاوری راد
[not found] ` <CAKTzs3QfN1FTrBuedprcw-TfAoHrgo8552VKWSOY=3K1p2WgHw@mail.gmail.com>
2018-08-07 9:29 ` Sitsofe Wheeler
2018-08-14 4:23 ` آرش خاوری راد
2018-08-14 8:11 ` Sitsofe Wheeler
2018-08-14 14:36 ` Alireza Haghdoost
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=CALjAwxh05QQRb1zLe_zkdbymHnjHOh-qaTPrXTwbMNJK4wXSKg@mail.gmail.com \
--to=sitsofe@gmail.com \
--cc=arash.khavary@gmail.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 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.