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

conf-sanity test_50g: /usr/bin/lfs setstripe failed: error on ioctl 0x4008669a: No data available

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • Lustre 2.10.0
    • None
    • 3
    • 9223372036854775807

    Description

      This issue was created by maloo for Andreas Dilger <andreas.dilger@intel.com>

      This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/91648930-0a62-11e7-b5b2-5254006e85c2.

      The sub-test test_50g failed with the following error in the test log:

      osc.lustre-OST0000-osc-ffff88000005d000.ost_server_uuid in FULL state after 0 sec
      error on ioctl 0x4008669a for '/mnt/lustre/f50g.conf-sanity' (3): No data available
      error: setstripe: create file '/mnt/lustre/f50g.conf-sanity' failed: No data available
       conf-sanity test_50g: @@@@@@ FAIL: /usr/bin/lfs setstripe failed 
      

      and the following error in the client debug log:

      lov_ea.c:185:lsm_unpackmd_common() lustre-clilov_UUID: OST index 1 more than OST count 1
      lov_pack.c:61:lov_dump_lmm_common() objid 0x1:7025, magic 0x0bd10bd0, pattern 0x1
      lov_pack.c:65:lov_dump_lmm_common() stripe_size 1048576, stripe_count 2, layout_gen 0
      lov_pack.c:84:lov_dump_lmm_objects() stripe 0 idx 1 subobj 0x0:34
      lov_pack.c:84:lov_dump_lmm_objects() stripe 1 idx 0 subobj 0x0:98
      lov_pack.c:308:lov_unpackmd() Process leaving rc=-22
      file.c:1671:ll_file_getstripe() Process entered
      cl_object.c:346:cl_object_getstripe() Process entered
      lov_object.c:1470:lov_object_getstripe() Process entered
      lov_object.c:1474:lov_object_getstripe() Process leaving rc=-61
      cl_object.c:356:cl_object_getstripe() Process leaving rc=-61
      file.c:1679:ll_file_getstripe() Process leaving rc=-61
      file.c:1707:ll_lov_setstripe() Process leaving rc=-61
      file.c:2384:ll_file_ioctl() Process leaving rc=-61
      

      so it looks like OSC for OST0001 is not set up properly, even though a file is striped across that OST. I'd think that the client would at least know about the OST, even if it was inactive.

      The first failure that I can see in the past 4 weeks is on 2017-03-15:
      https://testing.hpdd.intel.com/test_sets/b83305d2-0a7b-11e7-b5b2-5254006e85c2
      https://testing.hpdd.intel.com/test_sets/132e33a8-0a7c-11e7-9053-5254006e85c2
      https://testing.hpdd.intel.com/test_sets/4f302876-0981-11e7-8c9f-5254006e85c2
      https://testing.hpdd.intel.com/test_sets/96174724-0954-11e7-8c9f-5254006e85c2
      https://testing.hpdd.intel.com/test_sets/e43dbe38-0954-11e7-8c9f-5254006e85c2
      https://testing.hpdd.intel.com/test_sets/6b883f0a-093f-11e7-9053-5254006e85c2

      Info required for matching: conf-sanity 50g

      Attachments

        Issue Links

          Activity

            People

              wc-triage WC Triage
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: