[gpfsug-discuss] Getting 'blk_cloned_rq_check_limits: over max size limit' errors after updating the systems to kernel 2.6.32-642.el6 or later

[Jan-Frode Myklebust]

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 PM, Matt Weil <mweil at wustl.edu> wrote:

> 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 myself because I was
> adding new storage.
>
> Was wondering what version of GPFS fixes this.  I really do not want to
> step back to and older kernel version.
>
> Thanks
> Matt
>
> ________________________________
> The materials in this message are private and may contain Protected
> Healthcare Information or other information of a sensitive nature. If you
> are not the intended recipient, be advised that any unauthorized use,
> disclosure, copying or the taking of any action in reliance on the contents
> of this information is strictly prohibited. If you have received this email
> in error, please immediately notify the sender via telephone or return mail.
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170212/c306f8cf/attachment-0002.htm>