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

Test failure sanity test_133d: crossdir_rename_size error

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • Lustre 2.6.0
    • 3
    • 11422

    Description

      This issue was created by maloo for Nathaniel Clark <nathaniel.l.clark@intel.com>

      This issue relates to the following test suite run:
      http://maloo.whamcloud.com/test_sets/84c21dd4-43ee-11e3-8599-52540035b04c
      http://maloo.whamcloud.com/test_sets/05b9feb4-4027-11e3-9aa8-52540035b04c

      The sub-test test_133d failed with the following error:

      sanity.sh: line 8555: [: : integer expression expected
      crossdir_rename_size error

      Info required for matching: sanity 133d

      Attachments

        Issue Links

          Activity

            [LU-4203] Test failure sanity test_133d: crossdir_rename_size error

            Closing this as a duplicate of LU-5490 so that we only track a single issue and that bug gets more attention.

            adilger Andreas Dilger added a comment - Closing this as a duplicate of LU-5490 so that we only track a single issue and that bug gets more attention.
            bogl Bob Glossman (Inactive) added a comment - another on master in review-zfs-part-1: https://testing.hpdd.intel.com/test_sets/7e829b86-88cc-11e5-9053-5254006e85c2
            jamesanunez James Nunez (Inactive) added a comment - - edited Another instance on review-zfs for master: 2015-09-15 22:10:10 - https://testing.hpdd.intel.com/test_sets/b9bac8ee-5c36-11e5-aa2b-5254006e85c2 2015-10-21 15:27:24 - https://testing.hpdd.intel.com/test_sets/1f89e264-7829-11e5-9072-5254006e85c2 2016-01-09 09:54:51 - https://testing.hpdd.intel.com/test_sets/70a9d6d6-b6fe-11e5-a93d-5254006e85c2
            bogl Bob Glossman (Inactive) added a comment - - edited another on master: (zfs) https://testing.hpdd.intel.com/test_sets/d241dbb2-3cc1-11e5-8aeb-5254006e85c2
            jamesanunez James Nunez (Inactive) added a comment - This test has failed abut five times in the past month on master: 2015-05-04 17:54:09 - https://testing.hpdd.intel.com/test_sets/5b002ec0-f31d-11e4-bbef-5254006e85c2 2015-05-11 19:24:57 - https://testing.hpdd.intel.com/test_sets/ffae7506-f883-11e4-94ea-5254006e85c2 2015-05-13 04:51:16 - https://testing.hpdd.intel.com/test_sets/b06283e2-f9ab-11e4-bd86-5254006e85c2 2015-05-19 18:30:38 - https://testing.hpdd.intel.com/test_sets/21cc903c-fee7-11e4-a4ed-5254006e85c2 2015-06-03 09:12:27 - https://testing.hpdd.intel.com/test_sets/a46c8348-0a5a-11e5-b9ed-5254006e85c2

            In more recent test failures I've seen in the test output that the directory size as reported to "stat" does not match the size reported via the rename_stats file:

            mdt.lustre-MDT0000.rename_stats=clear
            source rename dir size: 512
            target rename dir size: 16K
            CMD: shadow-21vm4 /usr/sbin/lctl get_param mdt.*.rename_stats
            mdt.lustre-MDT0000.rename_stats=
            rename_stats:
            - snapshot_time:  1417878009.516837
            - crossdir_src   
                  512bytes: { sample:   1, pct: 100, cum_pct: 100 }
            - crossdir_tgt   
                  512bytes: { sample:   1, pct: 100, cum_pct: 100 }
            CMD: shadow-21vm4 /usr/sbin/lctl get_param mdt.*.rename_stats
            CMD: shadow-21vm4 /usr/sbin/lctl get_param mdt.*.rename_stats
            CMD: shadow-21vm4 /usr/sbin/lctl get_param mdt.*.rename_stats
             sanity test_133d: @@@@@@ FAIL: crossdir_rename_size error  
            

            and

            mdt.lustre-MDT0000.rename_stats=clear
            source rename dir size: 64K
            target rename dir size: 16K
            CMD: shadow-15vm8 /usr/sbin/lctl get_param mdt.*.rename_stats
            mdt.lustre-MDT0000.rename_stats=
            rename_stats:
            - snapshot_time:  1417662080.951886
            - crossdir_src   
                  32KB: { sample:   1, pct: 100, cum_pct: 100 }
            - crossdir_tgt   
                  512bytes: { sample:   1, pct: 100, cum_pct: 100 }
            CMD: shadow-15vm8 /usr/sbin/lctl get_param mdt.*.rename_stats
            CMD: shadow-15vm8 /usr/sbin/lctl get_param mdt.*.rename_stats
            CMD: shadow-15vm8 /usr/sbin/lctl get_param mdt.*.rename_stats
             sanity test_133d: @@@@@@ FAIL: crossdir_rename_size error  
            

            This is probably related to some internal implementation details of osd-zfs. or how it interacts with the mdt rename stats code. While it would generate somewhat confusing stats and causes testing failures, it doesn't appear to be a defect that would affect actual usage.

            adilger Andreas Dilger added a comment - In more recent test failures I've seen in the test output that the directory size as reported to "stat" does not match the size reported via the rename_stats file: mdt.lustre-MDT0000.rename_stats=clear source rename dir size: 512 target rename dir size: 16K CMD: shadow-21vm4 /usr/sbin/lctl get_param mdt.*.rename_stats mdt.lustre-MDT0000.rename_stats= rename_stats: - snapshot_time: 1417878009.516837 - crossdir_src 512bytes: { sample: 1, pct: 100, cum_pct: 100 } - crossdir_tgt 512bytes: { sample: 1, pct: 100, cum_pct: 100 } CMD: shadow-21vm4 /usr/sbin/lctl get_param mdt.*.rename_stats CMD: shadow-21vm4 /usr/sbin/lctl get_param mdt.*.rename_stats CMD: shadow-21vm4 /usr/sbin/lctl get_param mdt.*.rename_stats sanity test_133d: @@@@@@ FAIL: crossdir_rename_size error and mdt.lustre-MDT0000.rename_stats=clear source rename dir size: 64K target rename dir size: 16K CMD: shadow-15vm8 /usr/sbin/lctl get_param mdt.*.rename_stats mdt.lustre-MDT0000.rename_stats= rename_stats: - snapshot_time: 1417662080.951886 - crossdir_src 32KB: { sample: 1, pct: 100, cum_pct: 100 } - crossdir_tgt 512bytes: { sample: 1, pct: 100, cum_pct: 100 } CMD: shadow-15vm8 /usr/sbin/lctl get_param mdt.*.rename_stats CMD: shadow-15vm8 /usr/sbin/lctl get_param mdt.*.rename_stats CMD: shadow-15vm8 /usr/sbin/lctl get_param mdt.*.rename_stats sanity test_133d: @@@@@@ FAIL: crossdir_rename_size error This is probably related to some internal implementation details of osd-zfs. or how it interacts with the mdt rename stats code. While it would generate somewhat confusing stats and causes testing failures, it doesn't appear to be a defect that would affect actual usage.

            I suspect something strange with the /proc output when running on ZFS.

            adilger Andreas Dilger added a comment - I suspect something strange with the /proc output when running on ZFS.

            People

              jay Jinshan Xiong (Inactive)
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: