Re: Using FIO to benchmark Gluster

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux