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: Mon, 20 Dec 2021 17:38:07 +0300 [thread overview]
Message-ID: <7cc48a89-7bc3-bd55-733b-c9d40fecb0ab@cloudlinux.com> (raw)
In-Reply-To: <CACzyWQwCvsCkh=Ui_cr5Hh8jqZGEkX4B1YwujEnR6nYutjPveA@mail.gmail.com>
On 12/20/21 06:41, Seyed Mohammad Fakhraie wrote:
> I created a replica-3 setup on a single machine. It's description can
> be seen below:
>
> volume Name: gv1
> Type: Replicate
> Volume ID: 14fce60f-78e1-4021-9939-81abcd71f761
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x 3 = 3
> Transport-type: tcp
> Bricks:
> Brick1: storage-node-8:/data/brick1/gv1
> Brick2: storage-node-8:/data/brick2/gv1
> Brick3: storage-node-8:/data/brick3/gv1
> Options Reconfigured:
> transport.address-family: inet
> nfs.disable: on
> performance.client-io-threads: off
>
> I'm using Debian 10 with Gluster 5.5.
> After running the test using gfapi the same error showed itself during
> randread :
>
> failed fio extend file 1vm-1G-rand-read-3rep to 18446744073709551615
>
> The job file:
> [global]
> ioengine=gfapi
> volume=gv1
> brick=storage-node-8
> 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
Reproduced, I'll take a look. To make sure we're seeing the same issue, could you also check brick
logs (usually /var/log/glusterfs/bricks/pool-[whatever].log) for something similar to the following:
[2021-12-20 14:27:18.193027 +0000] E [MSGID: 113038] [posix-inode-fd-ops.c:5318:posix_ftruncate] 0-test0-posix: ftruncate failed on fd=0x13e5838 (-1 [Invalid argument]
[2021-12-20 14:27:18.193163 +0000] E [MSGID: 115063] [server-rpc-fops_v2.c:1214:server4_ftruncate_cbk] 0-test0-server: TRUNCATE info [{frame=50}, {FTRUNCATE_fd_no=0},
{uuid_utoa=1287dc8e-2896-4580-a14b-ef84ea9aad84}, {client=CTX_ID:3acbbb24-88af-48cd-9da0-62922a7855a3-GRAPH_ID:0-PID:671237-HOST:fedora-PC_NAME:test0-client-0-RECON_NO:-0}, {error-xlator=test0-posix},
{errno=22}, {error=Invalid argument}]
Dmitry
next prev parent reply other threads:[~2021-12-20 14:38 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 [this message]
[not found] ` <CACzyWQwe2SYR_W=XyuCk=THBZ-0frnh5u1gtjALfnZBpu6EerA@mail.gmail.com>
2021-12-21 9:34 ` Dmitry Antipov
[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=7cc48a89-7bc3-bd55-733b-c9d40fecb0ab@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.