On 09/18/2017 11:53 AM, kusumi.tomohiro@xxxxxxxxx wrote:
> From: Tomohiro Kusumi <tkusumi@xxxxxxxxxx>
>
> It could fail due to bs not multiple of sector size.
>
> Signed-off-by: Tomohiro Kusumi <tkusumi@xxxxxxxxxx>
> ---
> ioengines.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/ioengines.c b/ioengines.c
> index fa4acab..b8a31a8 100644
> --- a/ioengines.c
> +++ b/ioengines.c
> @@ -342,8 +342,8 @@ int td_io_queue(struct thread_data *td, struct io_u *io_u)
> td->o.odirect) {
>
> log_info("fio: first direct IO errored. File system may not "
> - "support direct IO, or iomem_align= is bad. Try "
> - "setting direct=0.\n");
> + "support direct IO, or iomem_align= is bad, or "
> + "invalid IO size. Try setting direct=0.\n");
Should that say "block size" or something instead of IO size? I think that
would be clearer.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
