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

sanity test_901: FAIL: mgs lock leak (34 != 37)

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • Lustre 2.14.0
    • None
    • 3
    • 9223372036854775807

    Description

      This issue was created by maloo for jianyu <yujian@whamcloud.com>

      This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/86cd8382-4a79-11ea-b58e-52540065bddc

      test_901 failed with the following error:

      == sanity test 901: don't leak a mgc lock on client umount =========================================== 05:31:29 (1581168689)
      CMD: trevis-17vm12 /usr/sbin/lctl get_param -n ldlm.namespaces.MGS*.lock_count
      10.9.4.209@tcp:/lustre /mnt/lustre lustre rw,flock,user_xattr,lazystatfs 0 0
      CMD: trevis-16vm11 grep -c /mnt/lustre' ' /proc/mounts
      Stopping client trevis-16vm11 /mnt/lustre (opts:)
      CMD: trevis-16vm11 lsof -t /mnt/lustre
      CMD: trevis-16vm11 umount  /mnt/lustre 2>&1
      Starting client: trevis-16vm11:  -o user_xattr,flock trevis-17vm12@tcp:/lustre /mnt/lustre
      CMD: trevis-16vm11 mkdir -p /mnt/lustre
      CMD: trevis-16vm11 mount -t lustre -o user_xattr,flock trevis-17vm12@tcp:/lustre /mnt/lustre
      CMD: trevis-17vm12 /usr/sbin/lctl get_param -n ldlm.namespaces.MGS*.lock_count
       sanity test_901: @@@@@@ FAIL: mgs lock leak (34 != 37) 
      

      <<Please provide additional information about the failure here>>

      VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
      sanity test_901 - mgs lock leak (34 != 37)

      Attachments

        Issue Links

          Activity

            People

              core-lustre-triage Core Lustre Triage
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: