On 03/01/2012 11:09 AM, Stefan Hübner wrote:
> Hi List,
>
> I'm using this FIO-job to stress-test iSCSI-Targets:
>
> [global]
> disable_lat=1
> disable_clat=1
> disable_slat=1
> clat_percentiles=0
> time_based
> runtime=${SECONDS}
> nice=10
> prio=5
> ioengine=libaio
> iodepth=16
> direct=1
> iomem_align=4M
> verify=crc32c-intel
> verify_async=2
> do_verify=1
> verify_dump=1
> [iSCSI]
> rw=randwrite
> bsrange=4k-4M
> filename=${ISCSI_DEVICE}
>
> ISCSI_DEVICE=/dev/sdX
> SECONDS=some value how long it should take
>
> When running this job I cannot see the verification taking place. I.e. network thruput to the target (writing) is happening at around 115MB/s, but thruput from the target (reading/verifying) doesn't exceed 2,7MB/s.
>
> Am I doing something wrong, here?
Does the fio job transition to the verify phase? You can see that in the
[] listing, a V would be the verify. When the job exits, it also shows
you both how many bytes were read and written. The read could should be
the verified part.
So please post the output of the job so we can take a closer look.
--
Jens Axboe
--
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
