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

SElinux : sanity test_17m: @@@@@@ FAIL: e2fsck should not report error upon short/long

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • Lustre 2.8.0
    • Tag 2.7.64
      1 Client, 2 OSTs , 1 MGT (Master)
    • 3
    • 9223372036854775807

    Description

      sanity test_17m failed for SElinux enabled client with the following error.

      test log:

      == sanity test 17m: run e2fsck against MDT which contains short/long symlink == 23:51:37 (1450223497)
      create 512 short and long symlink files under /mnt/lustre/d17m.sanitym
      erase them
      Waiting for local destroys to complete
      recreate the 512 symlink files with a shorter string
      stop and checking mds1: e2fsck -fnvd /dev/vda5
      Stopping /mnt/mdt0 (opts:) on eagle-52vm2
      eagle-52vm2: e2fsck 1.42.13.wc3 (28-Aug-2015)
      eagle-52vm2: e2fsck_pass1:1510: increase inode 243 badness 0 to 2
      eagle-52vm2: [QUOTA WARNING] Usage inconsistent for ID 0:actual (5808128, 1365) != expected (5926912, 1494)
      eagle-52vm2: [QUOTA WARNING] Usage inconsistent for ID 0:actual (5804032, 1364) != expected (5922816, 1493)
      Pass 1: Checking inodes, blocks, and sizes
      Pass 2: Checking directory structure
      Pass 3: Checking directory connectivity
      Unconnected directory inode 253 (/O/200000005/d2/???)
      Connect to /lost+found? no
      
      '..' in ... (253) is /O/200000005/d2 (251), should be <The NULL inode> (0).
      Fix? no
      
      Unconnected directory inode 255 (/O/200000005/d2/???/???)
      Connect to /lost+found? no
      
      '..' in ... (255) is /O/200000005/d2/??? (253), should be <The NULL inode> (0).
      Fix? no
      
      Pass 4: Checking reference counts
      Inode 251 ref count is 2, should be 3.  Fix? no
      
      Inode 255 ref count is 2, should be 1.  Fix? no
      
      Pass 5: Checking group summary information
      Update quota info for quota type 0? no
      
      Update quota info for quota type 1? no
      
      
      lustre-MDT0000: ********** WARNING: Filesystem still has errors **********
      
      
              1377 inodes used (0.14%, out of 1004400)
                40 non-contiguous files (2.9%)
                 3 non-contiguous directories (0.2%)
                   # of inodes with ind/dind/tind blocks: 11/0/0
            148977 blocks used (29.67%, out of 502086)
                 0 bad blocks
                 1 large file
      
               141 regular files
               185 directories
                 0 character device files
                 0 block device files
                 0 fifos
        4294967294 links
              1042 symbolic links (521 fast symbolic links)
                 0 sockets
      ------------
              1366 files
      Starting mds1:   /dev/vda5 /mnt/mdt0
      Started lustre-MDT0000
       sanity test_17m: @@@@@@ FAIL: e2fsck should not report error upon  short/long symlink MDT: rc=4 
        Trace dump:
        = /usr/lib64/lustre/tests/test-framework.sh:4822:error_noexit()
        = /usr/lib64/lustre/tests/test-framework.sh:4853:error()
        = /usr/lib64/lustre/tests/sanity.sh:613:test_17m()
        = /usr/lib64/lustre/tests/test-framework.sh:5100:run_one()
        = /usr/lib64/lustre/tests/test-framework.sh:5137:run_one_logged()
        = /usr/lib64/lustre/tests/test-framework.sh:5002:run_test()
        = /usr/lib64/lustre/tests/sanity.sh:616:main()
      Dumping lctl log to /tmp/test_logs/2015-12-15/193207/sanity.test_17m.*.1450223526.log
      eagle-52vm5: Host key verification failed.
      eagle-52vm5: rsync: connection unexpectedly closed (0 bytes received so far) [sender]
      eagle-52vm5: rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6]
      eagle-52vm2: Host key verification failed.
      eagle-52vm2: rsync: connection unexpectedly closed (0 bytes received so far) [sender]
      eagle-52vm2: rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]
      eagle-52vm3: Host key verification failed.
      eagle-52vm3: rsync: connection unexpectedly closed (0 bytes received so far) [sender]
      eagle-52vm3: rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]
      

      Attachments

        Issue Links

          Activity

            [LU-7568] SElinux : sanity test_17m: @@@@@@ FAIL: e2fsck should not report error upon short/long
            niu Niu Yawei (Inactive) added a comment - Dup of LU-7116 .

            Yes, very likely.

            niu Niu Yawei (Inactive) added a comment - Yes, very likely.
            sarah Sarah Liu added a comment -

            is this a dup of LU-7116?

            sarah Sarah Liu added a comment - is this a dup of LU-7116 ?
            sarah Sarah Liu added a comment -

            Hit the same issue when running sanity (sanity only) with 2.7.1 client and master server(tag-2.7.64) under DNE mode

            https://testing.hpdd.intel.com/test_sets/173b63f6-b575-11e5-bf32-5254006e85c2

            sarah Sarah Liu added a comment - Hit the same issue when running sanity (sanity only) with 2.7.1 client and master server(tag-2.7.64) under DNE mode https://testing.hpdd.intel.com/test_sets/173b63f6-b575-11e5-bf32-5254006e85c2

            Hi Niu,

            The system for newly formatted to latest Tag 2.7.64 and I ran a group of tests and one of them was sanity.sh. The sequence of group was as follows : runtest, fsx, sanityn, replay-single, recovery-small, replay-ost-single, insanity, sanity-quota, sanity.sh . And no , I never ran lfsck test on it.

            standan Saurabh Tandan (Inactive) added a comment - Hi Niu, The system for newly formatted to latest Tag 2.7.64 and I ran a group of tests and one of them was sanity.sh. The sequence of group was as follows : runtest, fsx, sanityn, replay-single, recovery-small, replay-ost-single, insanity, sanity-quota, sanity.sh . And no , I never ran lfsck test on it.

            Hi, Saurabh

            Is the system newly formatted or upgraded from old one? What kind of test did you run before the sanity? Have you ever run lfsck test?

            niu Niu Yawei (Inactive) added a comment - Hi, Saurabh Is the system newly formatted or upgraded from old one? What kind of test did you run before the sanity? Have you ever run lfsck test?

            I don't think it's related to the SELinux on client.

            The output shows some unconnected inodes.

            '..' in ... (253) is /O/200000005/d2 (251), should be <The NULL inode> (0).
            Fix? no

            One thing confused me is that where the directory "/O/200000005" come from? "200000005" is seq FID_SEQ_QUOTA. Di/Fanyong, will DNE or lfsck create this directory? Thanks.

            niu Niu Yawei (Inactive) added a comment - I don't think it's related to the SELinux on client. The output shows some unconnected inodes. '..' in ... (253) is /O/200000005/d2 (251), should be <The NULL inode> (0). Fix? no One thing confused me is that where the directory "/O/200000005" come from? "200000005" is seq FID_SEQ_QUOTA. Di/Fanyong, will DNE or lfsck create this directory? Thanks.
            pjones Peter Jones added a comment -

            Niu

            Could you please advise on this one?

            Peter

            pjones Peter Jones added a comment - Niu Could you please advise on this one? Peter

            People

              niu Niu Yawei (Inactive)
              standan Saurabh Tandan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: