I believe I have used thread and queue depth of at least 4 and ioengine is libaio.
Unfortunately, I have deleted by my fio job file.
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sitsofe Wheeler
Sent: Tuesday, 4 July, 2017 2:04 PM
To: Lim Chun Teck
Subject: [Bug 1400243] Re: fio just exits when -replay_iolog FILENAME is given
On Ubuntu 16.04 with fio-2.2.10 I cannot reproduce running against the nullblk device. I doubled up the dashes and ran like so:
Title:
fio just exits when -replay_iolog FILENAME is given
Status in fio package in Ubuntu:
New
Bug description:
Instead of replaying the io in the file specified, fio immediately
exits without submitting any io. On Ubuntu 12.04 32-bit, the same
option is working with fio-2.0.8-2. The particular version for this
Ubuntu 14.04 64-bit is fio-2.1.3-1. The iolog file is taken from a
-write_iolog option.
To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fio/+bug/1400243/+subscriptions
This e-mail and any attachments are only for the use of the intended recipient and may contain material that is confidential, privileged and/or protected by the Official Secrets Act. If you are not the intended recipient, please delete it or notify the sender immediately. Please do not copy or use it for any purpose or disclose the contents to any other person.
I believe I have used thread and queue depth of at least 4 and ioengine is libaio.
Unfortunately, I have deleted by my fio job file.
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sitsofe Wheeler
Sent: Tuesday, 4 July, 2017 2:04 PM
To: Lim Chun Teck
Subject: [Bug 1400243] Re: fio just exits when -replay_iolog FILENAME is given
On Ubuntu 16.04 with fio-2.2.10 I cannot reproduce running against the nullblk device. I doubled up the dashes and ran like so:
modprobe null_blk gb=100 4K-4K/4K- 4K, ioengine=sync, iodepth=1
cat <<EOF > fio-iolog-file
fio version 2 iolog
/dev/nullb0 add
/dev/nullb0 open
/dev/nullb0 read 5898366976 4096
/dev/nullb0 read 72397074432 4096
/dev/nullb0 read 82459553792 4096
/dev/nullb0 read 45965324288 4096
/dev/nullb0 read 39305207808 4096
/dev/nullb0 read 82160799744 4096
/dev/nullb0 read 13947228160 4096
/dev/nullb0 read 9487921152 4096
/dev/nullb0 read 76814397440 4096
/dev/nullb0 close
EOF
fio --ioengine=sync --name fio.iolog --read_iolog fio-iolog-file
fio.iolog: (g=0): rw=read, bs=4K-4K/
fio-2.2.10
Starting 1 process
fio.iolog: (groupid=0, jobs=1): err= 0: pid=27253: Tue Jul 4 07:03:06 2017
read : io=36864B, bw=36000KB/s, iops=9000, runt= 1msec
clat (usec): min=5, max=32, avg= 8.67, stdev= 8.79
lat (usec): min=5, max=32, avg= 8.78, stdev= 8.74
clat percentiles (usec):
| 1.00th=[ 5], 5.00th=[ 5], 10.00th=[ 5], 20.00th=[ 5],
| 30.00th=[ 5], 40.00th=[ 5], 50.00th=[ 6], 60.00th=[ 6],
| 70.00th=[ 7], 80.00th=[ 7], 90.00th=[ 32], 95.00th=[ 32],
| 99.00th=[ 32], 99.50th=[ 32], 99.90th=[ 32], 99.95th=[ 32],
| 99.99th=[ 32]
lat (usec) : 10=88.89%, 50=11.11%
cpu : usr=0.00%, sys=0.00%, ctx=0, majf=0, minf=5
IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
issued : total=r=9/w=0/d=0, short=r=0/w=0/d=0, drop=r=0/w=0/d=0
latency : target=0, window=0, percentile=100.00%, depth=1
Run status group 0 (all jobs):
READ: io=36KB, aggrb=36000KB/s, minb=36000KB/s, maxb=36000KB/s, mint=1msec, maxt=1msec
I wonder if this has been fixed in later fio releases...
-- /bugs.launchpad .net/bugs/ 1400243
You received this bug notification because you are subscribed to the bug report.
https:/
Title:
fio just exits when -replay_iolog FILENAME is given
Status in fio package in Ubuntu:
New
Bug description:
Instead of replaying the io in the file specified, fio immediately
exits without submitting any io. On Ubuntu 12.04 32-bit, the same
option is working with fio-2.0.8-2. The particular version for this
Ubuntu 14.04 64-bit is fio-2.1.3-1. The iolog file is taken from a
-write_iolog option.
======== terminal output ====== 4K-4K/4K- 4K, ioengine=sync, iodepth=1
$ sudo fio -name testlog -read_iolog fio-iolog-file
testlog: (g=0): rw=read, bs=4K-4K/
fio-2.1.3
Starting 1 process
Run status group 0 (all jobs):
===== end terminal output =======
======== fio-iolog-file ==========
fio version 2 iolog
/dev/sdb add
/dev/sdb open
/dev/sdb read 5898366976 4096
/dev/sdb read 72397074432 4096
/dev/sdb read 82459553792 4096
/dev/sdb read 45965324288 4096
/dev/sdb read 39305207808 4096
/dev/sdb read 82160799744 4096
/dev/sdb read 13947228160 4096
/dev/sdb read 9487921152 4096
/dev/sdb read 76814397440 4096
/dev/sdb close
====== end fio-iolog-file =======
ProblemType: Bug gnature: Ubuntu 3.13.0- 35.62-generic 3.13.11.6 Modules: dmhmap nvidia edia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
DistroRelease: Ubuntu 14.04
Package: fio 2.1.3-1
ProcVersionSi
Uname: Linux 3.13.0-35-generic x86_64
NonfreeKernel
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Dec 8 16:54:12 2014
InstallationDate: Installed on 2014-05-06 (216 days ago)
InstallationM
SourcePackage: fio
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to: /bugs.launchpad .net/ubuntu/ +source/ fio/+bug/ 1400243/ +subscriptions
https:/
This e-mail and any attachments are only for the use of the intended recipient and may contain material that is confidential, privileged and/or protected by the Official Secrets Act. If you are not the intended recipient, please delete it or notify the sender immediately. Please do not copy or use it for any purpose or disclose the contents to any other person.