Should io_limits/queue depth flushed persist while using verify_state?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



While using fio-2.2.4 the following snippet produces a verification
error for me on the second fio invocation:

fio --bs=4k --ioengine=libaio --direct=1 --verify=meta --iodepth=128
--io_limit=300k --verify_state_save=1 --rw=randwrite --name=write3
--filename=/dev/dm-7 && fio --bs=4k --ioengine=libaio --direct=1
--verify=meta --iodepth=128 --verify_state_load=1 --rw=randread
--name=write3 --filename=/dev/dm-7

However if I put the iodepth of the second fio command down to 64 or
set io_limit the error goes away. I have also sometimes seen an error
that looks similar if the first fio is killed via ctrl-C. Is this to
be expected?

-- 
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



[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux