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

sanity: e2fsck report error after create files under remote dir

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • None
    • None
    • 3
    • 16666

    Description

      This issue was created by maloo for Jodi Levi <jlevi@whamcloud.com>

      Please provide additional information about the failure here.

      This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/a592652a-75cd-11e4-b87d-5254006e85c2.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-6161 e2fsck failure after sanity.sh 65

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

          Activity

            [LU-5967] sanity: e2fsck report error after create files under remote dir
            adilger Andreas Dilger added a comment -

            Close as a duplicate of LU-6161

            adilger Andreas Dilger added a comment - Close as a duplicate of LU-6161
            adilger Andreas Dilger added a comment -

            It would have been easier to just change the description of this ticket instead of opening a new one, but I don't think it is needed to have two tickets open.

            adilger Andreas Dilger added a comment - It would have been easier to just change the description of this ticket instead of opening a new one, but I don't think it is needed to have two tickets open.
            di.wang Di Wang added a comment -

            reopen it for triage team to decide.

            di.wang Di Wang added a comment - reopen it for triage team to decide.
            di.wang Di Wang added a comment -

            create a new ticket LU-6161

            di.wang Di Wang added a comment - create a new ticket LU-6161
            di.wang Di Wang added a comment -

            reopen the issue for linking to the new ticket.

            di.wang Di Wang added a comment - reopen the issue for linking to the new ticket.
            di.wang Di Wang added a comment -

            This is different ticket. Not about remote directory. So I will close this one and open a new ticket.

            di.wang Di Wang added a comment - This is different ticket. Not about remote directory. So I will close this one and open a new ticket.
            di.wang Di Wang added a comment -

            I do not think this failure is related remote directory. 

            Inode 170393601 ref count is 1, should be 40.  Fix? no

            And also I checked the dmesg, it seems the test initially run runtests and sanity.sh 1-65, then restart acceptance test again without reformat the filesystem. So this e2fsck check failure should cause by some tests between 17n and test 65, probably some long existing bug. That said I do not think this is the critical ticket for 2.7.

            di.wang Di Wang added a comment - I do not think this failure is related remote directory. Inode 170393601 ref count is 1, should be 40. Fix? no And also I checked the dmesg, it seems the test initially run runtests and sanity.sh 1-65, then restart acceptance test again without reformat the filesystem. So this e2fsck check failure should cause by some tests between 17n and test 65, probably some long existing bug. That said I do not think this is the critical ticket for 2.7.
            jamesanunez James Nunez (Inactive) added a comment -

            I'm reopening this ticket since I've hit this problem with lustre-master tag 2.6.92 build #2812. Results are at https://testing.hpdd.intel.com/test_sets/37e63f92-9f0d-11e4-91b3-5254006e85c2 .

            jamesanunez James Nunez (Inactive) added a comment - I'm reopening this ticket since I've hit this problem with lustre-master tag 2.6.92 build #2812. Results are at https://testing.hpdd.intel.com/test_sets/37e63f92-9f0d-11e4-91b3-5254006e85c2 .
            di.wang Di Wang added a comment -

            Hmm, I can not reproduce it with master. And also I checked the maloo, and it seems the most recent failure happened in Nov 26th. So I guess the problem has been fixed somehow in master. I will close it for now. And please re-open it if it happens again.

            di.wang Di Wang added a comment - Hmm, I can not reproduce it with master. And also I checked the maloo, and it seems the most recent failure happened in Nov 26th. So I guess the problem has been fixed somehow in master. I will close it for now. And please re-open it if it happens again.
            jlevi Jodi Levi (Inactive) added a comment -

            Di,
            Could you please have a look at this one?
            Thank you!

            jlevi Jodi Levi (Inactive) added a comment - Di, Could you please have a look at this one? Thank you!

            People

              di.wang Di Wang
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: