On 11 April 2015 at 07:10, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: > On 11 April 2015 at 04:04, Samuel Shapiro <samuel.sh79@xxxxxxxxx> wrote: >> Well i guess it could be a good test for data integrity, so why not? :) >> >> On Fri, Apr 10, 2015 at 9:29 PM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: >>> On 8 April 2015 at 11:37, Samuel Shapiro <samuel.sh79@xxxxxxxxx> wrote: >>>> Hi All, >>>> >>>> [fsx-file-job1] >>>> directory=/mnt/FIO-some-mountpoint-to-NAS-01 >>>> ioengine=libaio >>>> iodepth=256 >>>> rw=randrw >>>> size=256k >>>> bs=4k >>>> norandommap >>> >>> ^^^ This allows the same block to be overwritten multiple times. Are >>> you sure this is what you want? > > I could be wide of the mark but my concern would be that meta tries to > verify block number (I guess this doesn't need to be saved and can be > calculated by just following a sequence). If I've overwritten a block > how do I verify that the block number of the earlier write was correct > - the block will in fact contain the block number of the last write to > it... Apologies, where I said block number I should have said "io sequence number" (because you're using verify=meta): Assuming I only do my verification at the end of a run, if I've overwritten a block how do I verify that the io sequence number of the earlier writes to that block were correct? Wouldn't the block will contain only the io sequence number of the last write to it? -- 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
