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

lctl in interactive mode repeated use of flags

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.7.0
    • Lustre 2.5.3
    • None
    • Centos 6.5
    • 3
    • 17566

    Description

      Flags passed to lctl subcommands in interactive are ignored after the first invocation. For example:

      % lctl
      lctl > get_param -n osc.knotfs-OST0037-osc-ffff8807eab68c00.cur_dirty_bytes
      0
      lctl > get_param -n osc.knotfs-OST0037-osc-ffff8807eab68c00.cur_dirty_bytes
      osc.knotfs-OST0037-osc-ffff8807eab68c00.cur_dirty_bytes=0
      lctl > get_param -n osc.knotfs-OST0037-osc-ffff8807eab68c00.cur_dirty_bytes
      osc.knotfs-OST0037-osc-ffff8807eab68c00.cur_dirty_bytes=0
      lctl >

      Expected behavior would be identical output all three times

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. LU-6268 lctl in interactive mode fails to parse get_param requests when run after get_param -n

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

          Bug - A problem which impairs or prevents the functions of the product. LU-6025 lctl nodemap commands stop working in interactive mode

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            [LU-6267] lctl in interactive mode repeated use of flags
            yujian Jian Yu added a comment -

            Hi Josh,

            The patch has landed. Let's close this ticket. If you still hit the issue, please feel free to reopen this ticket. Thank you.

            yujian Jian Yu added a comment - Hi Josh, The patch has landed. Let's close this ticket. If you still hit the issue, please feel free to reopen this ticket. Thank you.
            yujian Jian Yu added a comment -

            Hi Josh,
            Could you please try to use http://review.whamcloud.com/13893 to see whether it resolves the issues in LU-6267 and LU-6268 for you?

            yujian Jian Yu added a comment - Hi Josh, Could you please try to use http://review.whamcloud.com/13893 to see whether it resolves the issues in LU-6267 and LU-6268 for you?
            yujian Jian Yu added a comment -

            Here is the test result with the above patch on Lustre b2_5 branch:

            # lctl
lctl > get_param -n osc.lustre-OST0000-osc-ffff88007db75c00.cur_dirty_bytes
0
lctl > get_param -n osc.lustre-OST0000-osc-ffff88007db75c00.cur_dirty_bytes
0
lctl > get_param -n osc.lustre-OST0000-osc-ffff88007db75c00.cur_dirty_bytes
0
lctl >

            The patch can resolve the issue.

            yujian Jian Yu added a comment - Here is the test result with the above patch on Lustre b2_5 branch: # lctl lctl > get_param -n osc.lustre-OST0000-osc-ffff88007db75c00.cur_dirty_bytes 0 lctl > get_param -n osc.lustre-OST0000-osc-ffff88007db75c00.cur_dirty_bytes 0 lctl > get_param -n osc.lustre-OST0000-osc-ffff88007db75c00.cur_dirty_bytes 0 lctl > The patch can resolve the issue.
            yujian Jian Yu added a comment -

            Here is the back-ported patch for Lustre b2_5 branch: http://review.whamcloud.com/13893
            I'm verifying whether it resolves the issue in this ticket or not.

            yujian Jian Yu added a comment - Here is the back-ported patch for Lustre b2_5 branch: http://review.whamcloud.com/13893 I'm verifying whether it resolves the issue in this ticket or not.
            jlevi Jodi Levi (Inactive) added a comment -

            Yu Jian,
            Could you please look into this one and comment?
            Thank you!

            jlevi Jodi Levi (Inactive) added a comment - Yu Jian, Could you please look into this one and comment? Thank you!
            adilger Andreas Dilger added a comment -

            This might be a duplicate of LU-6025, which was just fixed recently. The patch to fix it was http://review.whamcloud.com/13063 and landed to master for 2.7.0.

            Even if that isn't the issue, it makes sense to use that patch to help narrow down if there is something else causing the problem.

            adilger Andreas Dilger added a comment - This might be a duplicate of LU-6025 , which was just fixed recently. The patch to fix it was http://review.whamcloud.com/13063 and landed to master for 2.7.0. Even if that isn't the issue, it makes sense to use that patch to help narrow down if there is something else causing the problem.

            People

              yujian Jian Yu
              jlothian Josh Lothian (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: