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

parallel-scale test_metabench: metabench failed with 1

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • None
    • Lustre 2.6.0
    • None
    • client and server: lustre-master build # 1911 RHEL6 ldiskfs
    • 3
    • 13091

    Description

      https://maloo.whamcloud.com/test_sets/2254277a-a030-11e3-947c-52540035b04c

      test log shows:

      [02/27/2014 12:30:13] Entering par_create_multidir to create 4343 files in 1 dirs
      Removed 30400 files in    205.132 seconds
      [02/27/2014 12:34:02] Leaving par_create_multidir
      Parallel file creation by 7 processes in seperate directories
      Process       Files       Time       Rate
      -------- ---------- ---------- ----------
      001/008        4343     23.758    182.805
      002/008        4343     18.392    236.135
      003/008        4343     23.868    181.957
      004/008        4343     18.325    236.996
      005/008        4343     23.885    181.828
      006/008        4343     18.388    236.186
      007/008        4343     23.927    181.510
      -------- ---------- ---------- ----------
      Total         30401     23.927   1270.568
      Elapsed       30401     23.928   1270.507
      -------- ---------- ---------- ----------
      Average        4343     21.506    205.345
      Std Dev                  2.718     26.932 (  12.64%) (  13.12%)
      
      [02/27/2014 12:36:47] FATAL error on process 0
      Proc 0: Unable to stat file [/mnt/lustre/d0.metabench/CREATE_MD_008.000/nSUFhBISq]: No such file or directory
      --------------------------------------------------------------------------
      mpirun has exited due to process rank 0 with PID 29305 on
      node client-32vm5 exiting improperly. There are two reasons this could occur:
      
      1. this process did not call "init" before exiting, but others in
      the job did. This can cause a job to hang indefinitely while it waits
      for all processes to call "init". By rule, if one process calls "init",
      then ALL processes must call "init" prior to termination.
      
      2. this process called "init", but exited without calling "finalize".
      By rule, all processes that call "init" MUST call "finalize" prior to
      exiting or it will be considered an "abnormal termination"
      
      This may have caused other processes in the application to be
      terminated by signals sent by mpirun (as reported here).
      --------------------------------------------------------------------------
       parallel-scale test_metabench: @@@@@@ FAIL: metabench failed! 1 
      

      Attachments

        Issue Links

          Activity

            People

              hongchao.zhang Hongchao Zhang
              sarah Sarah Liu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: