From: Jens Axboe <axboe@kernel.dk>
To: smitha sunder <sundersmitha@gmail.com>,
Sitsofe Wheeler <sitsofe@gmail.com>
Cc: fio <fio@vger.kernel.org>
Subject: Re: No I/O performed by windowsaio/get_io_u: zero buflen
Date: Sun, 16 Sep 2018 21:02:24 -0600 [thread overview]
Message-ID: <03bc8d3c-a8cb-fcbb-e7ff-f23a511f7908@kernel.dk> (raw)
In-Reply-To: <CA+zhgFR1V4yKg+gf0QUcuZy47R=-CqyK+_jKVJS4WKDtRb77hQ@mail.gmail.com>
On 9/16/18 5:24 PM, smitha sunder wrote:
> On Sun, Sep 16, 2018 at 3:02 PM, Sitsofe Wheeler <sitsofe@gmail.com> wrote:
>> On Sat, 15 Sep 2018 at 23:14, smitha sunder <sundersmitha@gmail.com> wrote:
>>>
>>> Hello all,
>>>
>>> I have a 30TB drive and I am running into an issue with random writes.
>>> I went through this thread :
>>> https://www.spinics.net/lists/fio/msg06294.html that seems to be fixed
>>> already.
>>
>> I think that was something different regarding different blocksizes
>> per direction.
>>
>>> I see the same issue with random reads as well.
>>> So not sure what is the issue here in my case; any help is greatly appreciated.
>>>
>>>
>>> Read Capacity results:
>>> Protection: prot_en=1, p_type=1, p_i_exponent=0 [type 2 protection]
>>> Logical block provisioning: lbpme=1, lbprz=1
>>> Last logical block address=58781073407 (0xdaf9fffff), Number of
>>> logical blocks=58781073408
>>> Logical block length=512 bytes
>>> Logical blocks per physical block exponent=3 [so physical block
>>> length=4096 bytes]
>>> Lowest aligned logical block address=0
>>> Hence:
>>> Device size: 30095909584896 bytes, 2.87017e+007 MiB, 30095.9 GB
>>>
>>>
>>> C:\Program Files (x86)\fio>fio --ioengine=windowsaio --group_reporting
>>> --direct=1 --size=100% --bs=4K --thread --filename=\\.\PhysicalDrive1
>>> --name=precond --rw=randwrite --iodepth=1 --numjobs=1
>>> --debug=io,random
>>
>> <snip>
>>
>>> io 3372 fill: io_u 0A458780:
>>> off=0x144365e7d000,len=0x0,ddir=1,file=\\.\PhysicalDrive1
>>> io 3372 get_io_u: zero buflen on 0A458780
>>> io 3372 get_io_u failed
>>> io 3372 drop page cache \\.\PhysicalDrive1
>>> random 3372 off rand 17311067694306724737
>>
>> That offset is crazy big - I'm sure it's bigger than a petabyte so my
>> guess is that something is overflowing. If you use --size=27g does the
>> job go through?
>>
>> [...]
>>
>>> I don’t see this issue if I use bs=8K or I use ba=512,8K, etc.
>>
>> --
>> Sitsofe | http://sucs.org/~sits/
> Hi Sitsofe,
>
> Thanks for the reply!
>
> Yes; If I use --size=27G or if provide the exact size that the OS
> displays, then the job goes through.
Are you running a 32-bit or 64-bit build of fio?
--
Jens Axboe
next prev parent reply other threads:[~2018-09-17 3:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 22:14 No I/O performed by windowsaio/get_io_u: zero buflen smitha sunder
2018-09-16 22:02 ` Sitsofe Wheeler
2018-09-16 23:24 ` smitha sunder
2018-09-17 3:02 ` Jens Axboe [this message]
2018-09-17 3:13 ` smitha sunder
2018-09-17 3:31 ` Jens Axboe
2018-09-17 3:34 ` smitha sunder
2018-09-17 3:41 ` Jens Axboe
2018-09-17 16:33 ` Smitha Sunder
2018-09-17 16:38 ` Jens Axboe
2018-09-17 3:45 ` Jens Axboe
2018-09-17 3:50 ` smitha sunder
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=03bc8d3c-a8cb-fcbb-e7ff-f23a511f7908@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sitsofe@gmail.com \
--cc=sundersmitha@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.