From: Jens Axboe <axboe@kernel.dk>
To: Robert Elliott <relliott@beardog.cce.hp.com>,
elliott@hp.com, fio@vger.kernel.org
Subject: Re: [PATCH] fio: print io_u errors on one line
Date: Tue, 16 Sep 2014 20:11:14 -0600 [thread overview]
Message-ID: <5418EDC2.6080203@kernel.dk> (raw)
In-Reply-To: <20140916220631.32299.39978.stgit@beardog.cce.hp.com>
On 2014-09-16 16:09, Robert Elliott wrote:
> From: Robert Elliott <elliott@hp.com>
>
> Print io_u errors on one line and with one log_err command
> to keep them from being interrupted by other prints
>
> Old:
> fio: io_u error on file /dev/sdt: Input/output error5.1MB/0KB/0KB /s]
> [227K/0/0 iops] [eta 02d:10h:53m:36s]
> read offset=145442430976, buflen=4096
> fio: io_u error on file /dev/sdt: Input/output error
> read offset=397760724992, buflen=4096
>
> New:
> fio: io_u error on file /dev/sdr: Input/output error: write offset=1532626153472, buflen=4096
> fio: io_u error on file /dev/sdt: Input/output error: write offset=102684229632, buflen=4096
Thanks, applied.
--
Jens Axboe
prev parent reply other threads:[~2014-09-17 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 22:09 [PATCH] fio: print io_u errors on one line Robert Elliott
2014-09-17 2:11 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5418EDC2.6080203@kernel.dk \
--to=axboe@kernel.dk \
--cc=elliott@hp.com \
--cc=fio@vger.kernel.org \
--cc=relliott@beardog.cce.hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox