Chun Teck
Subject: [Bug 1400243] Re: fio just exits when -replay_iolog FILENAME is given
Lim:
Can you confirm you were using fio-2.2.10 on Ubuntu 16.04)
William:
Since Lim has found this issue in the fio for Ubuntu 14.04 but it appears to be
fixed in the fio for 16.04 how does Lim proceed
Lim:
Can you confirm you were using fio-2.2.10 on Ubuntu 16.04)
William:
Since Lim has found this issue in the fio for Ubuntu 14.04 but it appears to be
fixed in the fio for 16.04 how does Lim proceed to close this?
--
You received this bug notification because you are a member of Ubuntu
oun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Sitsofe
Wheeler
Sent: Tuesday, 15 August, 2017 12:24 AM
To: Lim Chun Teck
Subject: [Bug 1400243] Re: fio just exits when -replay_iolog FILENAME is given
Lim:
The output you included says otherwise:
testlog: (g=0): rw=read, bs=4K-4K/4K-4K/
Lim:
The output you included says otherwise:
testlog: (g=0): rw=read, bs=4K-4K/4K-4K/4K-4K, ioengine=sync, iodepth=1
fio-2.1.3
I guess the main points are: Can this still be reproduced and if so can
what were the steps? Further, can it still be reproduced with stock fio
on Ubuntu 16.04 or later
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
cat < fio-iolog-file
fio version 2 iolog
/dev/nullb0
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
cat < fio-iolog-file
fio version 2 iolog
/dev/nullb0 add
/dev/nullb0 open
/dev/nullb0 read 5898366976 4096
/dev/nullb0 read 72397074432 4096
