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: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Matt Weil <mweil at wustl.edu> Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org> Date: Monday, February 13, 2017 at 9:46 AM To: "gpfsug-discuss at spectrumscale.org" <gpfsug-discuss at spectrumscale.org> Subject: [EXTERNAL] Re: [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 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170213/07c2cfe7/attachment.html>