On 2014-05-19 11:38, xan.peng wrote:
When specify invalidate=1 or fadvise_hint=1, fio will call posix_fadvise(2), which will return -EBADF and prevent fio librbd engine acting normally. Here is the call path: ... > td_io_open_file() > file_invalidate_cache() > __file_invalidate_cache() > posix_fadvise(fd = -1) > ... The patch work-around this problem by setting file type to FIO_TYPE_CHAR in fio_rbd_open().
Might be better to add a new type for this, like FIO_TYPE_SPECIAL or something. Otherwise we could risk running into other cases, where fio then thinks it really is a char device.
-- 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
