Hi ,
I am trying to do a data validation test on a NVMe drive with journaling enabled when I run the workload with -j in the config file for 100 seconds . I am saving the journal file in the local system.
I shutdown the system power in the middle of the vdbench run(between 80 and 100 seconds). I then restart the system and run a vdbench verification run with -jro option with journal=local path of journal file from previous run in config file. I am hitting data miscompare when I run the second vdbench run. I am running my test on Windows Server 2102 with vdbench50406.
I did some experiments and my understanding is that journal file is not getting updated continuously and hence is not in sync with dribve when the power is pulled suddenly to the system. Hence, when after server restart, I rerun the VDBench Data validation using the journal file, i get data miscompares.
Is my understanding correct? If yes , can I do something to test this power cycle data validation scenario?
here is how my vdbench profile file
/////////////////////////////////////////////////////////
*PowercycleWorkload: WOrkload to run Random 50% read write at different block sizes
*SD: Storage Definition
*WD: Workload Definition
*RD: Run Definition
*
data_errors=1
sd=sd1,lun=physicaldrive1,threads=2,journal=C:\Users\Administrator\Desktop\WindowsSystemPowerCycle\TC8,size=3125627568
wd=wd1,sd=sd1,xfersize=4k,rdpct=50,seekpct=100
rd=random_write_read,wd=wd1,iorate=max,elapsed=100,interval=1,forxfersize=(4k,16k)
/////////////////////////////////////////////////////