Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

log_offset seems to be getting ignores #928

Closed
garengllc opened this issue Feb 13, 2020 · 5 comments
Closed

log_offset seems to be getting ignores #928

garengllc opened this issue Feb 13, 2020 · 5 comments
Labels
patcheswelcome No one internal is working on this but an external contributor's help is very welcome! triaged Issue cause is understood but a patch is needed to fix it

Comments

@garengllc
Copy link

The log_offset flag seems to be getting ignored as well as defaulting to on.

My command is:

sudo LD_PRELOAD=/home/jason/epiq/speed/spdk/examples/nvme/fio_plugin/fio_plugin /home/jason/epiq/speed/fio/fio --name=write --ioengine=spdk --iodepth=4 --rw=write --bs=4k --direct=1 --runtime=3s --numjobs=8 --group_reporting --thread=1 --filename='trtype=PCIe traddr=0000.3b.00.0 ns=1' --log_offset=0 --write_bw_log=fio-test --write_iops_log=fio-test --write_lat_log=fio-test --per_job_logs=0

I am on fio-3.18. Leaving "--log_offset=0" off the command does the same thing.

And example snippet of fio-test_bw.log looks like:

0, 82732, 1, 4096, 0
0, 6509, 1, 4096, 0
0, 6486, 1, 4096, 0
0, 6477, 1, 4096, 0
0, 134215, 1, 4096, 0
0, 149707, 1, 4096, 0
0, 92350, 1, 4096, 0
0, 91044, 1, 4096, 0
0, 135777, 1, 4096, 0
0, 136597, 1, 4096, 0
0, 107763, 1, 4096, 0
0, 106761, 1, 4096, 0
0, 132065, 1, 4096, 0
0, 132299, 1, 4096, 0
0, 82889, 1, 4096, 0
0, 83694, 1, 4096, 0

Which of course means that tools/plot/fio2gnuplot doesn't work:

1 files Selected with pattern '*_bw.log'
 |-> fio-test_bw.log

Traceback (most recent call last):
  File "tools/plot/fio2gnuplot", line 532, in <module>
    sys.exit(main(sys.argv))
  File "tools/plot/fio2gnuplot", line 510, in main
    blk_size=compute_temp_file(fio_data_file,disk_perf,gnuplot_output_dir,min_time,max_time)
  File "tools/plot/fio2gnuplot", line 201, in compute_temp_file
    time, perf, x, block_size = line[1]
ValueError: too many values to unpack
@pzoxiuv
Copy link

pzoxiuv commented Feb 19, 2020

I think that last column isn't the offset but rather the priority bit which was introduced in b2a432b. It doesn't look like that commit lets you disable it.

You can easily patch fio2gnuplot to handle the extra column though: pzoxiuv@94b940a

@sitsofe
Copy link
Collaborator

sitsofe commented Jun 12, 2020

@pzoxiuv If your patch is generic would you like to submit it as a pull request?

@sitsofe
Copy link
Collaborator

sitsofe commented Jun 12, 2020

@trinof Could you submit a documentation update to

fio/HOWTO

Line 4161 in 14060eb

Log File Formats
and https://github.com/axboe/fio/blob/master/fio.1#L3861 in the light of the high priority bit logging change?

@sitsofe sitsofe added the triaged Issue cause is understood but a patch is needed to fix it label Jun 12, 2020
@trinof
Copy link
Contributor

trinof commented Jun 12, 2020

Sure, I'll send a small patch out

@sitsofe
Copy link
Collaborator

sitsofe commented Aug 1, 2020

Ping @pzoxiuv - would you like to submit a pull request?

@sitsofe sitsofe added the patcheswelcome No one internal is working on this but an external contributor's help is very welcome! label Aug 19, 2020
@axboe axboe closed this as completed in 2984a4f Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patcheswelcome No one internal is working on this but an external contributor's help is very welcome! triaged Issue cause is understood but a patch is needed to fix it
Projects
None yet
Development

No branches or pull requests

4 participants