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

Running lfs changelog with no registered user results in LBUG

Details

    • Bug
    • Resolution: Fixed
    • Blocker
    • Lustre 2.7.0
    • Lustre 2.7.0
    • None
    • Seen on master b6a3222, Robert confirmed he saw it on a master build from yesterday.
    • 3
    • 16400

    Description

      See the attached reproducer script for details.

      In short, running lfs changelog after deregistering the last registered user results in an LBUG on umount of the client. While it is obviously a user error to run lfs changelog with no registered users, it shouldn't result in an LBUG.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. LU-5877 lfs changelog hangs after lfs changelog_clear

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

          Bug - A problem which impairs or prevents the functions of the product. LU-5877 lfs changelog hangs after lfs changelog_clear

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

          Bug - A problem which impairs or prevents the functions of the product. LU-5038 Mount hangs for hours processing some llog

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

          Activity

            [LU-5859] Running lfs changelog with no registered user results in LBUG
            pjones Peter Jones added a comment -

            Landed for 2.7

            pjones Peter Jones added a comment - Landed for 2.7
            gerrit Gerrit Updater added a comment -

            Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13414/
            Subject: LU-5859 llog: do not cleanup orphans in remote catalogs
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 97df2f4cae374130c057cbf1168ad1427c96cbc5

            gerrit Gerrit Updater added a comment - Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13414/ Subject: LU-5859 llog: do not cleanup orphans in remote catalogs Project: fs/lustre-release Branch: master Current Patch Set: Commit: 97df2f4cae374130c057cbf1168ad1427c96cbc5
            gerrit Gerrit Updater added a comment -

            Alex Zhuravlev (alexey.zhuravlev@intel.com) uploaded a new patch: http://review.whamcloud.com/13414
            Subject: LU-5859 llog: do not cleanup orphans in remote catalogs
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: c418baa20e78da556916f48d5dc407fa6e4aab50

            gerrit Gerrit Updater added a comment - Alex Zhuravlev (alexey.zhuravlev@intel.com) uploaded a new patch: http://review.whamcloud.com/13414 Subject: LU-5859 llog: do not cleanup orphans in remote catalogs Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: c418baa20e78da556916f48d5dc407fa6e4aab50
            bzzz Alex Zhuravlev added a comment -

            Michael, looking at that now, thanks for reminding.

            bzzz Alex Zhuravlev added a comment - Michael, looking at that now, thanks for reminding.
            mjmac Michael MacDonald (Inactive) added a comment - - edited

            Hi. Just looking for a status update on this ticket. Seems like it should be a blocker... Any input, bzzz?

            mjmac Michael MacDonald (Inactive) added a comment - - edited Hi. Just looking for a status update on this ticket. Seems like it should be a blocker... Any input, bzzz ?
            adilger Andreas Dilger added a comment -

            Alex, could you please offer some advice on how to fix this problem? It was apparently introduced by your patch http://review.whamcloud.com/10308

            adilger Andreas Dilger added a comment - Alex, could you please offer some advice on how to fix this problem? It was apparently introduced by your patch http://review.whamcloud.com/10308
            mjmac Michael MacDonald (Inactive) added a comment -

            I confirm that LU-5038 seems to be the culprit. I reverted the commit in a local build and my reproducer script no longer causes an LBUG.

            mjmac Michael MacDonald (Inactive) added a comment - I confirm that LU-5038 seems to be the culprit. I reverted the commit in a local build and my reproducer script no longer causes an LBUG.

            People

              bfaccini Bruno Faccini (Inactive)
              mjmac Michael MacDonald (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: