Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-10510

Fix 'over max size limit' issue

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      Some sites have encountered issues with messages like:

      May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
May 10 13:54:50 oss02 kernel: device-mapper: multipath: Failing path 8:48.
May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
May 10 13:54:50 oss02 kernel: device-mapper: multipath: Failing path 8:240.

      This issue can cause corruption on storage side. It can be fixed by reverting an upstream patch or adding a udev script (but we will change max_sectors_kb value while mounting time, so it still can be triggered even with this script). The better way is to handle this value in mount.lustre tool. I'll make up a patch for master first.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-9132 Tuning max_sectors_kb on mount

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            [LU-10510] Fix 'over max size limit' issue
            adilger Andreas Dilger made changes -
            Link New: This issue is related to DDN-934 [ DDN-934 ]
            ys Yang Sheng made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            ys Yang Sheng made changes -
            Link New: This issue is duplicated by WK-31 [ WK-31 ]
            ys Yang Sheng made changes -
            Link New: This issue is duplicated by CTCH-29 [ CTCH-29 ]
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-9132 [ LU-9132 ]
            pjones Peter Jones made changes -
            Description Original: Many of customer site encountered issue with message like:
            {noformat}
            May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
            May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
            May 10 13:54:50 oss02 kernel: device-mapper: multipath: Failing path 8:48.
            May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
            May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
            May 10 13:54:50 oss02 kernel: device-mapper: multipath: Failing path 8:240.
            {noformat}
            This issue can cause badly corruption on storage side(e.g.INS-20,DELL-325). It can be fixed by revert upstream patch by https://review.whamcloud.com/28098. Also can be fixed by add a udev script. But we will change max_sectors_kb value while mounting time, So it still can be triggered even with this script. The better way is handle this value in mount.lustre tool like https://review.whamcloud.com/27265. I'll make up a patch for master first.

            		 New: Some sites have encountered issues with messages like:
            {noformat}
            May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
            May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
            May 10 13:54:50 oss02 kernel: device-mapper: multipath: Failing path 8:48.
            May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
            May 10 13:54:50 oss02 kernel: blk_cloned_rq_check_limits: over max size limit.
            May 10 13:54:50 oss02 kernel: device-mapper: multipath: Failing path 8:240.

            {noformat}
            This issue can cause corruption on storage side. It can be fixed by reverting an upstream patch or adding a udev script (but we will change max_sectors_kb value while mounting time, so it still can be triggered even with this script). The better way is to handle this value in mount.lustre tool. I'll make up a patch for master first.
            adilger Andreas Dilger made changes -
            Link New: This issue is related to PT-10 [ PT-10 ]
            ys Yang Sheng made changes -
            Link New: This issue is related to ISBC-103 [ ISBC-103 ]
            ys Yang Sheng created issue -

            People

              ys Yang Sheng
              ys Yang Sheng
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: