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

recovery-random-scale test_fail_client_mds: test_fail_client_mds returned 4

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Lustre 2.10.3
    • None
    • Failover
      Client/Server: 2.10.3 RC1
      b2_10, build 68
    • 3
    • 9223372036854775807

    Description

      recovery-random-scale test_fail_client_mds - test_fail_client_mds returned 4
      ^^^^^^^^^^^^^ DO NOT REMOVE LINE ABOVE ^^^^^^^^^^^^^

      This issue was created by maloo for Saurabh Tandan <saurabh.tandan@intel.com>

      This issue relates to the following test suite run:
      https://testing.hpdd.intel.com/test_sets/b02af984-f65d-11e7-94c7-52540065bddc

      test_fail_client_mds failed with the following error:

      test_fail_client_mds returned 4
      

      Test logs:

      ==== Checking the clients loads BEFORE failover -- failure NOT OK              ELAPSED=3962 DURATION=86400 PERIOD=1200
      10:34:00 (1515580440) waiting for onyx-41vm3 network 5 secs ...
      10:34:00 (1515580440) network interface is UP
      CMD: onyx-41vm3 rc=0;
      			val=\$(/usr/sbin/lctl get_param -n catastrophe 2>&1);
      			if [[ \$? -eq 0 && \$val -ne 0 ]]; then
      				echo \$(hostname -s): \$val;
      				rc=\$val;
      			fi;
      			exit \$rc
      CMD: onyx-41vm3 ps auxwww | grep -v grep | grep -q run_dd.sh
      Client load failed on node onyx-41vm3, rc=1
      2018-01-10 10:34:31 Terminating clients loads ...
      Duration:               86400
      Server failover period: 1200 seconds
      Exited after:           3962 seconds
      Number of failovers before exit:
      mds1 failed over 4 times
      Status: FAIL: rc=4
      CMD: onyx-41vm3,onyx-41vm4 test -f /tmp/client-load.pid &&
              { kill -s TERM \$(cat /tmp/client-load.pid); rm -f /tmp/client-load.pid; }
      onyx-41vm3: sh: line 1: kill: (8054) - No such process
      

      run_tar_debug.onyx-41vm4.log

      tar: etc/ssl: Cannot stat: No such file or directory
      tar: etc/systemd/system/getty.target.wants: Cannot stat: No such file or directory
      tar: etc/systemd/system/sockets.target.wants: Cannot stat: No such file or directory
      tar: etc/systemd/system/multi-user.target.wants: Cannot stat: No such file or directory
      tar: etc/systemd/system/sysinit.target.wants: Cannot stat: No such file or directory
      tar: etc/systemd/system/dev-virtio\\x2dports-org.qemu.guest_agent.0.device.wants: Cannot stat: No such file or directory
      tar: etc/systemd/system/remote-fs.target.wants: Cannot stat: No such file or directory
      tar: etc/systemd/system/basic.target.wants: Cannot stat: No such file or directory
      tar: etc/systemd/system/default.target.wants: Cannot stat: No such file or directory
      tar: etc/systemd/system: Cannot stat: No such file or directory
      tar: etc/systemd: Cannot stat: No such file or directory
      tar: etc/rc.d/rc1.d: Cannot stat: No such file or directory
      tar: etc/rc.d/rc3.d: Cannot stat: No such file or directory
      tar: etc/rc.d/rc2.d: Cannot stat: No such file or directory
      tar: etc/rc.d/rc4.d: Cannot stat: No such file or directory
      tar: etc/rc.d/rc0.d: Cannot stat: No such file or directory
      tar: etc/rc.d/rc5.d: Cannot stat: No such file or directory
      tar: etc/rc.d/rc6.d: Cannot stat: No such file or directory
      tar: etc/rc.d: Cannot stat: No such file or directory
      tar: etc/alternatives: Cannot stat: No such file or directory
      tar: Exiting with failure status due to previous errors
      

      Attachments

        Issue Links

          Activity

            People

              mdilger Max Dilger
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: