From 4f7e57a42e348a643e0b7d50356597ded7010b83 Mon Sep 17 00:00:00 2001 From: Jens Axboe Date: Fri, 30 Mar 2012 21:21:20 +0200 Subject: [PATCH] Enhance the reaped status display Instead of just printing a '_' for a job that has exited, allow the user to tell if the job exited with an error or not. A normally reaped job that ran to completion without errors will have the '_' displayed. If the job exited with an error, then an 'X' will be displayed instead. Signed-off-by: Jens Axboe --- HOWTO | 7 +++++-- eta.c | 5 ++++- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/HOWTO b/HOWTO index 5622349f..62c70cb4 100644 --- a/HOWTO +++ b/HOWTO @@ -1339,13 +1339,16 @@ I Thread initialized, waiting. F Running, currently waiting for fsync() V Running, doing verification of written data. E Thread exited, not reaped by main thread yet. -_ Thread reaped. +_ Thread reaped, or +X Thread reaped, exited with an error. The other values are fairly self explanatory - number of threads currently running and doing io, rate of io since last check (read speed listed first, then write speed), and the estimated completion percentage and time for the running group. It's impossible to estimate runtime of -the following groups (if any). +the following groups (if any). Note that the string is displayed in order, +so it's possible to tell which of the jobs are currently doing what. The +first character is the first job defined in the job file, and so forth. When fio is done (or interrupted by ctrl-c), it will show the data for each thread, group of threads, and disks in that order. For each data diff --git a/eta.c b/eta.c index 6118d1af..4ad67629 100644 --- a/eta.c +++ b/eta.c @@ -18,7 +18,10 @@ static void check_str_update(struct thread_data *td) switch (td->runstate) { case TD_REAPED: - c = '_'; + if (td->error) + c = 'X'; + else + c = '_'; break; case TD_EXITED: c = 'E'; -- 2.25.1