You are doing ~4KB I/Os and driving a queue depth of <1. If you are
seeking all over the disk and mixing reads and writes, you may very well
trigger bad behaviour like this for SATA disks.
To further diagnose the issue, I'd recommend running blktrace on one of
the devices. If you report results here, could you also include more
information about the hardware, the storage layout (including any dm/md
drivers and file systems involved) and the workload? Also, please let
us know which I/O scheduler you're using.
Are you sure it was a kernel change that caused the issue? In other
words, can you run with the 2.6.32 and confirm that the issue is not
present?
Thanks,
Jeff
--