Add recommendation to set direct=0 if first O_DIRECT fails
authorJens Axboe <axboe@fb.com>
Tue, 28 Apr 2015 21:23:21 +0000 (15:23 -0600)
committerJens Axboe <axboe@fb.com>
Tue, 28 Apr 2015 21:23:21 +0000 (15:23 -0600)
commit44cc9c8fccd1862045ef029dc9a484c4a2e46731
treef70ff2031e128f3932f85ddfdbed147705e5d035
parent9451b93e81fb950a80da09e295e56b1ad4538509
Add recommendation to set direct=0 if first O_DIRECT fails

Fio currently tells you:

"fio: first direct IO errored. File system may not support direct IO, or
 iomem_align= is bad."

but it doesn't offer a remedy. Add a suggestion to set direct=0 if this
happens. It can happen because of a badly configured job, or from
blktrace replay because the latter adds direct=1 automatically. But that
may fail, if the trace contains IO that isn't sector aligned.

Signed-off-by: Jens Axboe <axboe@fb.com>
ioengines.c