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

mmp: test_10: @@@@@@ FAIL: e2fsck /tmp/lustre-ost1 on ost1failover returned 8

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.6.0
    • Lustre 2.5.0
    • 3
    • 11479

    Description

      The following command fails:

      mds_HOST=oss1 \
      ost1_HOST=oss1 \
      ost2_HOST=oss1 \
      PDSH="pdsh -R ssh -S -w" \
      ONLY=10 sh mmp.sh

      == mmp test 10: e2fsck with mounted filesystem ======================================================= 09:52:17 (1383749537)
      ..
      Running e2fsck on the device /tmp/lustre-ost1 on ost1failover...
      e2fsck 1.41.9 (22-Aug-2009)
      e2fsck: No such file of directory while trying to open /tmp/lustre-ost1

      The superblock could not be read or does not describe a correct ext2
      filesystem. If the device is valid and it really contains an ext2
      filesystem (and not swap or ufs or something else), then the superblock
      is corrupt, and you might try running e2fsck with an alternate superblock:
      e2fsck -b 8193 <device>

      mmp test_10: @@@@@@ FAIL: e2fsck /tmp/lustre-ost1 on ost1failover returned 8

      This is probably because test-framework.sh:facet_host() maps ostNfailover to $HOSTNAME when ost_HOST and ostNfailover_HOST are not defined and ignores defined ostN_HOST.

      Attachments

        Activity

          People

            cliffw Cliff White (Inactive)
            vsaveliev Vladimir Saveliev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: