All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Antipov <dantipov@cloudlinux.com>
To: Seyed Mohammad Fakhraie <fk.smoh@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Using FIO to benchmark Gluster
Date: Tue, 21 Dec 2021 12:34:58 +0300	[thread overview]
Message-ID: <f3ac3012-b641-d95c-5b73-315979842114@cloudlinux.com> (raw)
In-Reply-To: <CACzyWQwe2SYR_W=XyuCk=THBZ-0frnh5u1gtjALfnZBpu6EerA@mail.gmail.com>

On 12/20/21 19:11, Seyed Mohammad Fakhraie wrote:

> Hello Dmitry, Thanks for reaching out.
> by "reproduced", you mean that you're getting the same error during
> randomread workloads using gfapi? This is the error that I'm getting
> on all the setups that I've tested (3x Replica & 2x Replica with
> Arbiter) during randomread + gfapi:
> 
> failed fio extend file 4vm-1G-randrw.1.0 to 18446744073709551615

Definitely. What I'm seeing is:

# cat test0.fio
[global]
ioengine=gfapi
volume=test0
brick=localhost
direct=1
create_on_open=1
ramp_time=1m
iodepth=1
numjobs=1
openfiles=1
bs=4k
[1vm-1G-rand-read-3rep]
filesize=1G
time_based
runtime=3min
rw=randread
write_bw_log=4k-read-3replica-ro.results
write_iops_log=4k-read-3replica-ro.results
write_lat_log=4k-read-3replica-ro.results

# fio --debug=file test0.fio
fio: set debug option file
file     155116 dup files: 0
file     155116 add file 1vm-1G-rand-read-3rep.0.0
file     155116 resize file array to 2 files
file     155116 file 0x7fb75dbfa110 "1vm-1G-rand-read-3rep.0.0" added at 0
1vm-1G-rand-read-3rep: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=gfapi, iodepth=1
fio-3.28
Starting 1 process
file     155116 setup files
file     155116 get file size for 0x7fb75dbfa110/0/1vm-1G-rand-read-3rep.0.0
file     155116 get file size 1vm-1G-rand-read-3rep.0.0
file     155126 fio setup 0x1962ea0
file     155126 trying file 1vm-1G-rand-read-3rep.0.0 280
file     155126 fio file 1vm-1G-rand-read-3rep.0.0 open mode rw td rw read
file     155126 fio extend file 1vm-1G-rand-read-3rep.0.0 from 0 to 18446744073709551615
failed fio extend file 1vm-1G-rand-read-3rep.0.0 to 18446744073709551615
file     155126 fio 0x1962ea0 created 1vm-1G-rand-read-3rep.0.0
file     155126 error 1 on open of 1vm-1G-rand-read-3rep.0.0
file     155126 get_next_file_rr: (nil)
file     155126 get_next_file: NULL
file     155126 close files

This looks like a weird error parsing job file. I didn't get the logic
behind get_file_sizes(), but the job file definitely requests 1G ant not
18446744073709551615, which is -1ULL.

Dmitry

  parent reply	other threads:[~2021-12-21  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 16:01 Using FIO to benchmark Gluster Seyed Mohammad Fakhraie
2021-11-24 16:24 ` Dmitry Antipov
     [not found]   ` <CACzyWQzih6gCQ4vYGA9Hwj-Zq4_d+YKC1j=secP8W9nr7bZCgg@mail.gmail.com>
2021-11-25 15:18     ` Dmitry Antipov
     [not found]       ` <CACzyWQwCvsCkh=Ui_cr5Hh8jqZGEkX4B1YwujEnR6nYutjPveA@mail.gmail.com>
2021-12-20 14:38         ` Dmitry Antipov
     [not found]           ` <CACzyWQwe2SYR_W=XyuCk=THBZ-0frnh5u1gtjALfnZBpu6EerA@mail.gmail.com>
2021-12-21  9:34             ` Dmitry Antipov [this message]
     [not found]               ` <CACzyWQy7MXp619uJhJ=uDWqabT_xwt=6bu=Z5103twPJJMz1=A@mail.gmail.com>
2021-12-21 11:35                 ` Dmitry Antipov

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=f3ac3012-b641-d95c-5b73-315979842114@cloudlinux.com \
    --to=dantipov@cloudlinux.com \
    --cc=fio@vger.kernel.org \
    --cc=fk.smoh@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.