On Mon, May 19, 2014 at 07:38:51PM +0200, Sebastian Ott wrote:
> Hello,
>
> on the latest kernel a fio job with 4 workers using libaio hangs.
Is more than one process stuck in state D when the hang occurs? If so,
what does a backtrace show for the stuck processes (or are there any
hung process warnings issued)? It is entirely possible the bug isn't
caused by the referenced commit, as the commit you're pointing to merely
makes io_destroy() syscall wait for all aio outstanding to complete
before returning.
-ben
> git bisect points to:
> commit e02ba72aabfade4c9cd6e3263e9b57bf890ad25c
> Author: Anatol Pomozov <[email protected]>
> Date: Tue Apr 15 11:31:33 2014 -0700
>
> aio: block io_destroy() until all context requests are completed
>
>
> The fio workers are on the wait_for_completion in sys_io_destroy.
>
> Regards,
> Sebastian
> [global]
> blocksize=4K
> size=256M
> rw=randrw
> verify=md5
> iodepth=32
> ioengine=libaio
> direct=1
> end_fsync=1
>
> [file1]
> filename=/dev/scma
>
> [file2]
> filename=/dev/scmbw
>
> [file3]
> filename=/dev/scmc
>
> [file4]
> filename=/dev/scmx
--
"Thought is the essence of where you are now."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
