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

add dmesg -c to conf-sanity_83

Details

    • Bug
    • Resolution: Won't Fix
    • Minor
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      conf sanity 83 may fail with message:

      conf-sanity test_83: @@@@@@ FAIL: VFS: Busy inodes after unmount of vdb. Self-destruct in 5 seconds. Have a nice day...

      Dmesg clearing is needed in conf-sanity 83 because previous tests
      (for example conf-sanity_62) may also be the results of message "VFS: Busy inodes after unmount of ...".

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. LU-7227 Add a check to t-f that dmesg doesn't have critical messages

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

          Activity

            [LU-7706] add dmesg -c to conf-sanity_83
            adilger Andreas Dilger added a comment -

            Landed patch from LU-7227 instead.

            adilger Andreas Dilger added a comment - Landed patch from LU-7227 instead.
            adilger Andreas Dilger added a comment -

            New lustre code or fix may introduce "missed iput" and "VFS: busy inodes" as result. And it is better to find this error in testing if possible.

            Right, so we should detect this failure even if it happened in a previous test, so erasing the previous messages isn't helpful. The fix in LU-7227 seems a lot better, since it catches the failure right away. I don't recall seeing that bug/patch, but I'd think it better to abandon this patch and ticket in favor of that one.

            adilger Andreas Dilger added a comment - New lustre code or fix may introduce "missed iput" and "VFS: busy inodes" as result. And it is better to find this error in testing if possible. Right, so we should detect this failure even if it happened in a previous test, so erasing the previous messages isn't helpful. The fix in LU-7227 seems a lot better, since it catches the failure right away. I don't recall seeing that bug/patch, but I'd think it better to abandon this patch and ticket in favor of that one.
            scherementsev Sergey Cheremencev added a comment -

            The problem is fixed right now(in seagate) - it needs a kernel fix. But I didn't send it upstream yet.
            If you also face this problem("busy inodes" after conf-sanity 62) I can send it faster or make a kernel patch for lustre.

            conf-sanity_83 checks that there is no "busy inodes" messages caused by ENOSPACE on OST.
            Why Does it need to fail when message is caused by another issue(theoretically not lustre related issue) ?
            Even if the "busy inodes" after conf-sanity 62 will disappear there is no guarantee that another test will not cause the same message.

            Earlier in https://jira.hpdd.intel.com/browse/LU-7227 I suggested to fail tests that lead to kernel errors like "VFS: Busy inodes ..."
            New lustre code or fix may introduce "missed iput" and "VFS: busy inodes" as result. And it is better to find this error in testing if possible.

            scherementsev Sergey Cheremencev added a comment - The problem is fixed right now(in seagate) - it needs a kernel fix. But I didn't send it upstream yet. If you also face this problem("busy inodes" after conf-sanity 62) I can send it faster or make a kernel patch for lustre. conf-sanity_83 checks that there is no "busy inodes" messages caused by ENOSPACE on OST. Why Does it need to fail when message is caused by another issue(theoretically not lustre related issue) ? Even if the "busy inodes" after conf-sanity 62 will disappear there is no guarantee that another test will not cause the same message. Earlier in https://jira.hpdd.intel.com/browse/LU-7227 I suggested to fail tests that lead to kernel errors like "VFS: Busy inodes ..." New lustre code or fix may introduce "missed iput" and "VFS: busy inodes" as result. And it is better to find this error in testing if possible.
            adilger Andreas Dilger added a comment -

            It seems bad that any test causes the "VFS: Buay inodes ..." message to be hit. It would be better to find and fix that problem rather than working around this to allow the test to pass.

            adilger Andreas Dilger added a comment - It seems bad that any test causes the "VFS: Buay inodes ..." message to be hit. It would be better to find and fix that problem rather than working around this to allow the test to pass.
            gerrit Gerrit Updater added a comment -

            Sergey Cheremencev (sergey_cheremencev@xyratex.com) uploaded a new patch: http://review.whamcloud.com/18122
            Subject: LU-7706 tests: add dmesg -c to conf-sanity_83
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: dca4bf26e5177ece36d6d528106f1b033424c6d3

            gerrit Gerrit Updater added a comment - Sergey Cheremencev (sergey_cheremencev@xyratex.com) uploaded a new patch: http://review.whamcloud.com/18122 Subject: LU-7706 tests: add dmesg -c to conf-sanity_83 Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: dca4bf26e5177ece36d6d528106f1b033424c6d3

            People

              wc-triage WC Triage
              scherementsev Sergey Cheremencev
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: