fio基础16

verify=strIfwritingtoafile,fiocanverifythefilecontentsaftereachiterationofthejob.Eachverificationmethodalsoimpliesverificationofspecialheader,whichiswrittentothebeginningofeachblock.Thisheaderalsoincludesmetainformation,likeoffsetoftheblock,blocknumber,timestampwhenblockwaswritten,etc.verify=strcanbecombinedwithverify_pattern=stroption.Theallowedvaluesare:md5Useanmd5sumofthedataareaandstoreitintheheaderofeachblock.crc64Useanexperimentalcrc64sumofthedataareaandstoreitintheheaderofeachblock.crc32cUseacrc32csumofthedataareaandstoreitintheheaderofeachblock.crc32c-intelUsehardwareassistedcrc32ccalcuationprovidedonSSE4.2enabledprocessors.Fallsbacktoregularsoftwarecrc32c,ifnotsupportedbythesystem.crc32Useacrc32sumofthedataareaandstoreitintheheaderofeachblock.crc16Useacrc16sumofthedataareaandstoreitintheheaderofeachblock.crc7Useacrc7sumofthedataareaandstoreitintheheaderofeachblock.xxhashUsexxhashasthechecksumfunction.Generallythefastestsoftwarechecksumthatfiosupports.sha512Usesha512asthechecksumfunction.sha256Usesha256asthechecksumfunction.sha1Useoptimizedsha1asthechecksumfunction.metaThisoptionisdeprecated,sincenowmetainformationisincludedingenericverificationheaderandmetaverificationhappensbydefault.Fordetailedinformationseethedescriptionoftheverify=strsetting.Thisoptioniskeptbecauseofcompatibility's sake with old configurations. Do not use it. pattern Verify a strict pattern. Normally fio includes a header with some basic information and checksumming, but if this option is set, only the specific pattern set with 'verify_pattern' is verified. null Only pretend to verify. Useful for testing internals with ioengine=null, not for much else. This option can be used for repeated burn-in tests of a system to make sure that the written data is also correctly read back. If the data direction given is a read or random read, fio will assume that it should verify a previously written file. If the data direction includes any form of write, the verify will be of the newly written data. verifysort=bool If set, fio will sort written verify blocks when it deems it faster to read them back in a sorted manner. This is often the case when overwriting an existing file, since the blocks are already laid out in the file system. You can ignore this option unless doing huge amounts of really fast IO where the red-black tree sorting CPU time becomes significant. verify_offset=int Swap the verification header with data somewhere else in the block before writing. Its swapped back before verifying. verify_interval=int Write the verification header at a finer granularity than the blocksize. It will be written for chunks the size of header_interval. blocksize should divide this evenly. verify_pattern=str If set, fio will fill the io buffers with this pattern. Fio defaults to filling with totally random bytes, but sometimes it'sinterestingtofillwithaknownpatternforioverificationpurposes.Dependingonthewidthofthepattern,fiowillfill1/2/3/4bytesofthebufferatthetime(itcanbeeitheradecimalorahexnumber).Theverify_patterniflargerthana32-bitquantityhastobeahexnumberthatstartswitheither"0x"or"0X".Usewithverify=str.Also,verify_patternsupports%oformat,whichmeansthatforeachblockoffsetwillbewrittenandthenverifyiedback,e.g.:verify_pattern=%oOrusecombinationofeverything:verify_pattern=0xff%o"abcd"-12