From: Jens Axboe <axboe@kernel.dk>
To: bin lin <lbin186@gmail.com>
Cc: fio <fio@vger.kernel.org>
Subject: Re: fio: first direct io errored
Date: Thu, 19 Apr 2012 20:49:52 +0200 [thread overview]
Message-ID: <4F905E50.9070303@kernel.dk> (raw)
In-Reply-To: <CAOipSa2xmUmcNTFT5SSBJ0CnDHEpZVmkekWuSf5BnC47u_s3zA@mail.gmail.com>
On 2012-04-19 15:56, bin lin wrote:
> Hi, i am a newer with fio. i have written a read_iolog and use fio to
> run the trace in a
>
> device /dev/sdb1, but it had errors when add --direct=1. the errors is
> as follows:
>
> replay: (g=0): rw=read, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1
> fio 2.0.6
> Starting 1 process
> fio: first direct IO errored. File system may not support direct IO,
> or iomem_align= is bad.
> fio: pid=6363, err=22/file:engines/sync.c:62, func=xfer, error=Invalid argument
>
> the trace file is as follows:
> fio version 2 iolog
> /dev/sdb1 add
> /dev/sdb1 open
> /dev/sdb1 read 27267456 8
> /dev/sdb1 read 27267560 8
> /dev/sdb1 read 34933120 8
> /dev/sdb1 read 34933128 8
> /dev/sdb1 read 34933136 8
> /dev/sdb1 read 34933144 8
> /dev/sdb1 read 34604888 8
> /dev/sdb1 close
>
> The filesystem on /dev/sdb1 is ext3 which supports the O_DIRECT, and
> the trace file use
>
> block size as 512 byte. I do not know where the error is and how to
> solve it ? thanks
What job generated that iolog? The reason is fails is that the transfer
size is 8 _bytes_, it's not sectors. So the above wont work on any
device.
--
Jens Axboe
next prev parent reply other threads:[~2012-04-19 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 13:56 fio: first direct io errored bin lin
2012-04-19 18:49 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-30 12:53 fio: first direct IO errored Christian Zoffoli
2010-10-31 1:53 ` Jens Axboe
2010-10-31 12:13 ` Christian Zoffoli
2010-10-31 12:28 ` Jens Axboe
2010-10-31 12:38 ` Christian Zoffoli
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=4F905E50.9070303@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=lbin186@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.