--verify_pattern=%o increments with block size (BS) rather than some other more natural size

[yurzo]

#!/usr/bin/env bash
SIZE=32K
COMMON="--size=$SIZE --io_size=$SIZE --direct=1 --ioengine=libaio --name=carlos"
COMMON="$COMMON --verify_pattern=%o0xFFFFAAAABBBBCCCC"
COMMON="$COMMON --verify=pattern"
rm *.bin
rm *.hex
../fio/fio --rw=write $COMMON --bs=512 --filename=test1.bin
../fio/fio --rw=write $COMMON --bs=4K --filename=test2.bin
../fio/fio --rw=read $COMMON --bs=4K --filename=test1.bin
../fio/fio --rw=read $COMMON --bs=512 --filename=test2.bin
../fio/fio --rw=read $COMMON --bs=512 --filename=test1.bin
../fio/fio --rw=read $COMMON --bs=4K --filename=test2.bin

This precludes laying down a offset derived pattern and reading them with a different bs.
I naively expected the %o to increment with the native device block size.

[yurzo]

I think I now understand the --verify_interval option should take care of this. #522 notwithstanding