Details

    • Bug
    • Resolution: Fixed
    • Critical
    • Lustre 2.4.0, Lustre 2.1.6
    • Lustre 2.4.0, Lustre 2.1.4
    • None
    • 3
    • 7394

    Description

      We are using lustre 2.1.4-3chaos on our server clusters.

      Running a test application, one of our archive storage folks discovered that Lustre's directory listings are rather unreliable. The first thing she noticed is that directory entries can appear multiple times:

      > cd /p/lscratchrza/apotts/divt_rzstagg0/htar_1st_27475
      > find . -type f > ../test.lst0 ; echo $? ; wc -l ../test.lst0
      0
      34339 ../test.lst0
      > find . -type f > ../test.lst1 ; echo $? ; wc -l ../test.lst1
      0
      35006 ../test.lst1
      

      When the two directory listings are sorted and run through uniq, there are only 34339 unique entries.

      One of our sysadmins investigated, and further found that sometimes entry listing are missing altogether. But when the missing files are checked with an ls, they are present.

      This has been noticed with the above find command, and also using "/bin/ls -laR .". Both files and subdirectories have appeared twice in the directory listing.

      The Lustre clients that have reproduced this behaviour are running 2.1.2-4chaos and 1.8.5.0-6chaos.

      Attachments

        Activity

          [LU-3029] Directory listings are unreliable
          pjones Peter Jones added a comment -

          Excellent - thanks Ned!

          pjones Peter Jones added a comment - Excellent - thanks Ned!
          nedbass Ned Bass (Inactive) made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Peter, yes I believe we've had no further reports of this issue since we rolled out the patch. Marking resolved.

          nedbass Ned Bass (Inactive) added a comment - Peter, yes I believe we've had no further reports of this issue since we rolled out the patch. Marking resolved.
          pjones Peter Jones added a comment -

          A version of this patch has landed for both 2.4.0 and 2.1.6. Has LLNL been able to confirm that this work does correct the issue? Are we able to mark this issue as resolved?

          pjones Peter Jones added a comment - A version of this patch has landed for both 2.4.0 and 2.1.6. Has LLNL been able to confirm that this work does correct the issue? Are we able to mark this issue as resolved?
          pjones Peter Jones made changes -
          Fix Version/s New: Lustre 2.1.6 [ 10292 ]
          pjones Peter Jones made changes -
          Labels Original: mq213 ptr
          pjones Peter Jones made changes -
          Priority Original: Blocker [ 1 ] New: Critical [ 2 ]
          morrone Christopher Morrone (Inactive) made changes -
          Affects Version/s New: Lustre 2.4.0 [ 10154 ]
          pjones Peter Jones made changes -
          Fix Version/s New: Lustre 2.4.0 [ 10154 ]
          pjones Peter Jones made changes -
          Labels Original: ptr New: mq213 ptr

          People

            yong.fan nasf (Inactive)
            morrone Christopher Morrone (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: