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

sanity test_57b failure: 'MDC before 15214812 != after 15214800'

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.6.0, Lustre 2.5.2
    • Lustre 2.5.0
    • 3
    • 11065

    Description

      While testing HSM features, acceptance-small was run with test results at: https://maloo.whamcloud.com/test_sessions/4574cfe8-35e1-11e3-b051-52540035b04c

      From the test_log:

      == sanity test 57b: default LOV EAs are stored inside large inodes ===== 13:06:10 (1381781170)
      mcreating 100 files
      total: 100 creates in 0.17 seconds: 572.16 creates/second
      Filesystem           1K-blocks      Used Available Use% Mounted on
      mds@o2ib:/scratch     25088052    942228  22886476   4% /lustre/scratch
      opening files to create objects/EAs
      Filesystem           1K-blocks      Used Available Use% Mounted on
      mds@o2ib:/scratch     25088052    942228  22886720   4% /lustre/scratch
       sanity test_57b: @@@@@@ FAIL: MDC before 15214812 != after 15214800 
        Trace dump:
        = /usr/lib64/lustre/tests/test-framework.sh:4264:error_noexit()
        = /usr/lib64/lustre/tests/test-framework.sh:4291:error()
        = /usr/lib64/lustre/tests/sanity.sh:4670:test_57b()
        = /usr/lib64/lustre/tests/test-framework.sh:4530:run_one()
        = /usr/lib64/lustre/tests/test-framework.sh:4563:run_one_logged()
        = /usr/lib64/lustre/tests/test-framework.sh:4433:run_test()
        = /usr/lib64/lustre/tests/sanity.sh:4678:main()
      

      Attachments

        Issue Links

          Activity

            [LU-4109] sanity test_57b failure: 'MDC before 15214812 != after 15214800'

            Ok it was also my understanding that if LOV EA can not fit into MDT inode this will need at least 1 additional block per file, so in this case why not do the reverse test and simply detect if the number of free blocks decreased of 100+ blocks ?

            bfaccini Bruno Faccini (Inactive) added a comment - Ok it was also my understanding that if LOV EA can not fit into MDT inode this will need at least 1 additional block per file, so in this case why not do the reverse test and simply detect if the number of free blocks decreased of 100+ blocks ?

            Bruno, test_57b is trying to detect if the LOV EA is too large to fit into the MDT inode for some reason (e.g. formatted with too-small inodes, default LOV EA becomes too large, etc). If 100 files are created and 100 blocks are allocated then the test fails. In this case, only a few blocks are allocated (e.g. llog files, ChangeLog, etc), and the test shouldn't fail, so increasing the margin a small amount is fine.

            adilger Andreas Dilger added a comment - Bruno, test_57b is trying to detect if the LOV EA is too large to fit into the MDT inode for some reason (e.g. formatted with too-small inodes, default LOV EA becomes too large, etc). If 100 files are created and 100 blocks are allocated then the test fails. In this case, only a few blocks are allocated (e.g. llog files, ChangeLog, etc), and the test shouldn't fail, so increasing the margin a small amount is fine.

            Bruno,
            The file system was set up and run with pretty much all default settings. I think the striping for this set of tests was a single stripe with a single OSS with two OSTs. So, default striping, but not wide.

            James

            jamesanunez James Nunez (Inactive) added a comment - Bruno, The file system was set up and run with pretty much all default settings. I think the striping for this set of tests was a single stripe with a single OSS with two OSTs. So, default striping, but not wide. James

            Andreas, I would like to better understand what sanity/test_57b() tries to detect.
            So, what could cause this ? Wide default striping vs Inode size at mke2fs ?
            If yes, we could anticipate it and use/compute an appropriated margin, no ? If no, what did I miss and misunderstand?

            James, do you remember these parameters value during your failing test ?

            bfaccini Bruno Faccini (Inactive) added a comment - Andreas, I would like to better understand what sanity/test_57b() tries to detect. So, what could cause this ? Wide default striping vs Inode size at mke2fs ? If yes, we could anticipate it and use/compute an appropriated margin, no ? If no, what did I miss and misunderstand? James, do you remember these parameters value during your failing test ?

            Should be trivial to increase the margin from 8 to 16 or something. Since we create 100 files in the test, we should still be pretty safe.

            adilger Andreas Dilger added a comment - Should be trivial to increase the margin from 8 to 16 or something. Since we create 100 files in the test, we should still be pretty safe.
            pjones Peter Jones added a comment -

            Bruno

            Could you please help with this one?

            Thanks

            Peter

            pjones Peter Jones added a comment - Bruno Could you please help with this one? Thanks Peter

            People

              bfaccini Bruno Faccini (Inactive)
              jamesanunez James Nunez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: