Hi, Perhaps I answered the wrong question. If *fio is doing I/O verification for itself* (i.e. http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-verify is set etc.) then when fio verification fails it will report EILSEQ (which with glibc will be reported as "Invalid or incomplete multibyte or wide character" - see https://www.spinics.net/lists/fio/msg04977.html for details) whereas other errors will turn up as a different error message (e.g. EIO). For example: $ dd if=/dev/zero of=/tmp/fiofile bs=16k count=1 $ ./fio --name=verifymismatch --ioengine=sync --rw=read --verify=crc32c --filename=/tmp/fiofile --verify_fatal=1 verifymismatch: (g=0): rw=read, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=sync, iodepth=1 fio-3.0-48-g83a9 Starting 1 process verify: bad magic header 0, wanted acca at file /tmp/fiofile offset 0, length 4096 verifymismatch: No I/O performed by sync, perhaps try --debug=io option for details? fio: pid=3702, err=84/file:io_u.c:1991, func=io_u_sync_complete, error=Invalid or incomplete multibyte or wide character verifymismatch: (groupid=0, jobs=1): err=84 (file:io_u.c:1991, func=io_u_sync_complete, error=Invalid or incomplete multibyte or wide character): pid=3702: Tue Sep 12 22:55:51 2017 read: IOPS=62, BW=250KiB/s (256kB/s)(4096B/16msec) [...] Is that what you were after? On 12 September 2017 at 06:42, Udi-Yehuda Tamar <udi@xxxxxxxxxxxx> wrote: > > I'm using only libaio and I'm parsing the output Json file > I was looking to see if there is a unique msg for data corruption but > it's look like every other IO error > > On Mon, Sep 11, 2017 at 10:43 PM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: >> >> Different I/O engines may be able to return different types of error >> depending on what they are talking to and what level they operate at. >> For example the sg ioengine sets a timeout of 30 seconds but it looks >> like this still makes error handling kick in (see >> http://sg.danny.cz/sg/p/sg_v3_ho.html#id2495241 ). -- Sitsofe | http://sucs.org/~sits/ -- 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
