I realise most people are using Fio to do performance testing, ie replicating Windows IOMeter. But surely there are some guys using Fio for data integrity testing, could you guys give me some help with this ? On 10 August 2012 15:16, Gary Foster <gpfwestie@xxxxxxxxx> wrote: > > Hi all. > > I've been running some random IO tests where I want to verify the data > was written correctly. > > I have set norandommap=1 as I was running out of memory, but the man > page indicates > the data will not be verified > > --- cut --- > norandommap > Normally fio will cover every block of the file when > doing random I/O. If this parameter is given, a new offset will be > chosen without looking at past I/O history. This > parameter is mutually exclusive with verify. > -- cut ---- > > However, the output to stdio seems to indicate it is verifying (see > the 'V' below) - but is it really verifying > anything ? and if so, whats the difference between the verify with > norandommap being set to 0 ? > > -- cut --- > fio 2.0.7 > Starting 13 processes > bs: 13 (f=13): [wVwwwwwwwwwww] [0.0% done] [3695K/3679K /s] [902 /898 > iops] [eta 84d:23h:10m:19s] > -- cut -- > > Here's my job file > > [global] > blocksize=4K > readwrite=randwr > ioengine=libaio > verify=crc32c > verify_backlog=10 > iodepth=1 > direct=1 > norandommap=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
