Page tree
Skip to end of metadata
Go to start of metadata

Systems Description

  • Three nodes in total
    • MGS: MRtest01
    • OSS: MRtest02
    • Client: MRtest03


The goal of this instruction set is to describe how to setup tests to run on a local VM setup. The end target is to ease the debugging burden.

  1. Install Lustre RPMs on all your test nodes
  2. Install pdsh
    1. el6:,distro=el6/lastSuccessfulBuild/artifact/_topdir/RPMS/x86_64/
      1. pdsh-rcmd-ssh-2.29-1.wc1.x86_64.rpm
      2. pdsh-2.29-1.wc1.x86_64.rpm
    2. el7:,distro=el7/lastSuccessfulBuild/artifact/_topdir/RPMS/x86_64/
      1. pdsh-rcmd-ssh-2.29-1.wc1.x86_64.rpm
      2. pdsh-2.29-1.wc1.x86_64.rpm
  3. Setup passwordless ssh login among all nodes:
    2. YOU HAVE TO make sure that the node which you run the tests on can ssh passwordlessly into itself
    3. Make sure to ssh into all the nodes to get rid of any prompts.
  4. Insure that lustre-iokit* is installed on all the nodes
    1. yum install  lustre-iokit-2.8.50-
  5. Setup the /etc/hosts file to map hostname to ip address on all nodes. 
    1.               localhost.localdomain localhost         MRtest01 MRtest01.localdomain         MRtest02 MRtest02.localdomain         MRtest03 MRtest03.localdomain
      ::1             localhost6.localdomain6 localhost6



  6. Setup the /usr/lib64/lustre/tests/cfg/ to reflect your setup on the client (where you'll be running the tests). Modify this file by adding the below at the top of the file. No need to change anything else in the file.

    1. #file system name
      # mount point on the client
      # hostname of the mds
      # hostname of the mds (repeated as above)
      # mount point on the mds
      # number of MDSs in the test setup
      # physical device to formate using mkfs.lustre for the MDS
      # number of OSTs in the system.
      # host name of the OST
      # host name of the OST (repeated as above)
      # physical device to format using mkfs.lustre for the OST
      # OST mount point
      # PDSH command
      PDSH="pdsh -S -Rssh -w"
  7. Run

    1. go to /usr/lib64/lustre/tests/

    2. ./
    3. This will create and mount the file system. If this succeeds the filesystem should be in place.
  8. Run a test (or subtest)
    1. cd /usr/lib64/lustre/tests/
    2. ./auster -v --only 0a
      1. You can add '-r' to auster to avoid calling
    3. you should see something like
      1. [root@MRtest03 tests]# ./auster -v --only 0a
        Started at Tue Apr  5 12:36:03 PDT 2016
        MRtest03.localdomain: Checking config lustre mounted on /mnt/client
        Checking servers environments
        Checking clients MRtest03.localdomain environments
        Logging to local directory: /tmp/test_logs/2016-04-05/123602
        running: ONLY=0a 
        run_suite sanity /usr/lib64/lustre/tests/
        -----============= acceptance-small: sanity ============----- Tue Apr  5 12:36:09 PDT 2016
        Running: bash /usr/lib64/lustre/tests/
        MRtest03.localdomain: Checking config lustre mounted on /mnt/client
        Checking servers environments
        Checking clients MRtest03.localdomain environments
        Using TIMEOUT=20
        disable quota as required
        running as uid/gid/euid/egid 500/500/500/500, groups:
         [touch] [/mnt/client/d0_runas_test/f11819]
        excepting tests: 76 42a 42b 42c 42d 45 51d 68b
        skipping tests SLOW=no: 24o 24D 27m 64b 68 71 77f 78 115 124b 300o
        preparing for tests involving mounts
        mke2fs 1.42.13.wc4 (28-Nov-2015)
        == sanity test 0a: touch; rm ======================= 12:36:18 (1459884978)
        /mnt/client/f0a.sanity has type file OK
        /mnt/client/f0a.sanity: absent OK
        Resetting fail_loc on all nodes...done.
        PASS 0a (2s)
        resend_count is set to 4
        resend_count is set to 4
        resend_count is set to 4
        resend_count is set to 4
        resend_count is set to 4
        == sanity test complete, duration 17 sec == 12:36:26 (1459884986)
        debug=super ioctl neterror warning dlmtrace error emerg ha rpctrace vfstrace config console lfsck returned 0
        Finished at Tue Apr  5 12:36:27 PDT 2016 in 25s
        ./auster: completed with rc 0
  9. Auster usage help
    1. Usage auster [options]  suite [suite options] [suite [suite options]]
      Run Lustre regression tests suites.
            -c CONFIG Test environment config file
            -d LOGDIR Top level directory for logs
            -D FULLLOGDIR Full directory for logs
            -f STR    Config name (cfg/<name>.sh)
            -g GROUP  Test group file (Overrides tests listed on command line)
            -S TESTSUITE First test suite to run allows for restarts
            -i N      Repeat tests N times (default 1). A new directory
                      will be created under LOGDIR for each iteration.
            -k        Don't stop when subtests fail
            -R        Remount lustre between tests
            -r        Reformat (during initial configuration if needed)
            -s        SLOW=yes
            -v        Verbose mode
            -l        Send logs to the Maloo database after run
                        (can be done later by running
            -h        This help.
      Suite options
      These are suite specific options that can be specified after each suite on
      the command line.
         suite-name  [options]
            --only LIST         Run only specific list of subtests
            --except LIST       Skip list of subtests
            --start-at SUBTEST  Start testing from subtest
            --stop-at SUBTEST   Stop testing at subtest
            --time-limit LIMIT  Don't allow this suite to run longer
                                than LIMT seconds. [UNIMPLEMENTED]
      Example usage:
      Run all of sanity and all of replay-single except for 70b with SLOW=y using
      the default "local" configuration.
        auster -s sanity replay-single --except 70b
      Run all tests in the regression group 5 times using large config.
        auster -f large -g test-groups/regression -i 5


Testing a Lustre filesystem

Lustre Test Tools Environment Variables

Test Variable Definitions

Lustre Test Tools Environment Variables

  • No labels