On Tue, Apr 04 2017, kusumi.tomohiro@xxxxxxxxx wrote: > From: Tomohiro Kusumi <tkusumi@xxxxxxxxxx> > > Some runtime configurations can cause threads/processes to terminate > without any I/O performed, yet with no explicit error message, which > is quite confusing. In the example below, fio finishes with neither > error nor regular statistics due to file offset + bs being larger > than the file size while in get_io_u(). > > This commit calls log_err() when this happens. Since it's difficult > to tell the exact reason after thread has left the main I/O loop[*], > it gives advice to use a command line option --debug=io, similar to > the way td_io_init() gives advice. > > [*] It can't just replace dprint(FD_IO, ...) calls with td_verror() > for e.g. while in get_io_u(), since those are also used by non error > paths too. Thanks, applied 1-2, and 4-7. -- 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
