See this technote for an alternative fix and details:
http://www-01.ibm.com/support/docview.wss?uid=isg3T1024840=danl_4184_web
Bob Oesterlin
Sr Principal Storage Engineer, Nuance
From: on behalf of Matt Weil
Reply-To: gpfsug main
Alas, I ran into this as well – only seems to impact some my older JBOD
storage. The fix is vague, should I be worried about this turning up later, or
will it happen right away? (if it does)
Bob Oesterlin
Sr Principal Storage Engineer, Nuance
From:
excellent Thanks.
On 2/12/17 11:30 AM, Jan-Frode Myklebust wrote:
The 4.2.2.2 readme says:
* Fix a multipath device failure that reads "blk_cloned_rq_check_limits: over
max size limit" which can occur when kernel function bio_get_nr_vecs() returns
a value which is larger than the value of max
The 4.2.2.2 readme says:
* Fix a multipath device failure that reads "blk_cloned_rq_check_limits:
over max size limit" which can occur when kernel function bio_get_nr_vecs()
returns a value which is larger than the value of max sectors of the block
device.
-jf
On Sat, Feb 11, 2017 at 7:32
https://access.redhat.com/solutions/2437991
I ran into this issue the other day even with the echo "4096" >
/sys/block/$ii/queue/max_sectors_kb; in place. I have always made that
larger to get to the 2M IO size. So I never really seen this issue
until the other day. I may have triggered it