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

sanityn test_32b: @@@@@@ FAIL: lockless i/o works when disabled

Details

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

    Attachments

      Issue Links

        Activity

          [LU-10403] sanityn test_32b: @@@@@@ FAIL: lockless i/o works when disabled

          James, I see that each run in my local vm, so you may be right about time gap.

          tappro Mikhail Pershin added a comment - James, I see that each run in my local vm, so you may be right about time gap.

          So I attempted to reproduce the problem locally and I can't. It passes sanityn 32b. I have a theory why it fails. Using seconds is to large of a time gap. The pages are not being purged because the time that passes is less than one second. I bet if I move to nanoseconds this problem will go away.

          simmonsja James A Simmons added a comment - So I attempted to reproduce the problem locally and I can't. It passes sanityn 32b. I have a theory why it fails. Using seconds is to large of a time gap. The pages are not being purged because the time that passes is less than one second. I bet if I move to nanoseconds this problem will go away.

          suspect it may be due to time64_t being signed while cfs_time_t is unsigned

          bogl Bob Glossman (Inactive) added a comment - suspect it may be due to time64_t being signed while cfs_time_t is unsigned

          Oh that is strange. I will track down what the conflict is. Thanks.

          simmonsja James A Simmons added a comment - Oh that is strange. I will track down what the conflict is. Thanks.
          pjones Peter Jones added a comment -

          Should have been fixed by revert of offending patch

          pjones Peter Jones added a comment - Should have been fixed by revert of offending patch

          I've done git bisect and it shows commit 4f2a5d5887492da9abe320074511811415e0a06c as source of problem. This is change https://review.whamcloud.com/#/c/30063/ from LU-9019.

          This change passed own tests so it seems that issue is result of interaction with some other patch, anyway, reverting of this particular patch solves the problem

          tappro Mikhail Pershin added a comment - I've done git bisect and it shows commit 4f2a5d5887492da9abe320074511811415e0a06c as source of problem. This is change https://review.whamcloud.com/#/c/30063/ from LU-9019 . This change passed own tests so it seems that issue is result of interaction with some other patch, anyway, reverting of this particular patch solves the problem

          People

            simmonsja James A Simmons
            tappro Mikhail Pershin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: