Now those two support combined input and 'verify_pattern' supports '%o' format. Update corresponding doc. Signed-off-by: Roman Pen <r.peniaev@xxxxxxxxx> Cc: fio@xxxxxxxxxxxxxxx --- fio.1 | 35 +++++++++++++++++++++++++++++++++-- 1 file changed, 33 insertions(+), 2 deletions(-) diff --git a/fio.1 b/fio.1 index 5f8e948..7c13409 100644 --- a/fio.1 +++ b/fio.1 @@ -507,7 +507,26 @@ If set, fio will fill the IO buffers with this pattern. If not set, the contents of IO buffers is defined by the other options related to buffer contents. The setting can be any pattern of bytes, and can be prefixed with 0x for hex values. It may also be a string, where the string must then be wrapped with -"". +"", e.g.: +.RS +.RS +\fBbuffer_pattern\fR="abcd" +.RS +or +.RE +\fBbuffer_pattern\fR=-12 +.RS +or +.RE +\fBbuffer_pattern\fR=0xdeadface +.RE +.LP +Also you can combine everything together in any order: +.LP +.RS +\fBbuffer_pattern\fR=0xdeadface"abcd"-12 +.RE +.RE .TP .BI dedupe_percentage \fR=\fPint If set, fio will generate this percentage of identical buffers when writing. @@ -1167,7 +1186,19 @@ pattern for io verification purposes. Depending on the width of the pattern, fio will fill 1/2/3/4 bytes of the buffer at the time(it can be either a decimal or a hex number). The verify_pattern if larger than a 32-bit quantity has to be a hex number that starts with either "0x" or "0X". Use with -\fBverify\fP=meta or \fBverify\fP=pattern. +\fBverify\fP=meta or \fBverify\fP=pattern. Also, verify_pattern supports %o +format, which means that for each block offset will be written and then +verifyied back, e.g.: +.RS +.RS +\fBverify_pattern\fR=%o +.RE +Or use combination of everything: +.LP +.RS +\fBverify_pattern\fR=0xff%o"abcd"-21 +.RE +.RE .TP .BI verify_fatal \fR=\fPbool If true, exit the job on the first observed verification failure. Default: -- 2.5.1 -- 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
