I'm not totally sure if this is a user-error thing or a bug, but it appears the --section command is broken. Using 1.36 and the surface-scan example job (included below), I get the following output: # fio --showcmd surface-scan fio --thread=1 --bs=64k --direct=1 --ioengine=sync --verify=meta --verify_pattern=0xaa555aa5 --verify_interval=512 --name=write-phase --rw=write --fill_device=1 --do_verify=0 --filename=datafile.tmp --name=verify-phase --stonewall --create_serialize=0 --rw=read --do_verify=1 --filename=datafile.tmp # fio --showcmd surface-scan --section 'write-phase' fio --thread=1 --bs=64k --direct=1 --ioengine=sync --verify=meta --verify_pattern=0xaa555aa5 --verify_interval=512 Basically, it's only getting the global bits of the jobfile. So am I doing something wrong to identify the section or is this a bug? There does not seem to be a check to see if the specified section exists so that might be something to add. I've tried moving the order around, different quotations, etc. but haven't had any luck. ; writes 512 byte verification blocks until the disk is full, ; then verifies written data [global] thread=1 bs=64k direct=1 ioengine=sync verify=meta verify_pattern=0xaa555aa5 verify_interval=512 [write-phase] filename=datafile.tmp ; or use a full disk, for example /dev/sda rw=write fill_device=1 do_verify=0 [verify-phase] stonewall create_serialize=0 filename=datafile.tmp rw=read do_verify=1 Regards, Daniel -- 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
