Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-1309

Test format verify gets EBUSY return

    • Type: Icon: Task Task
    • Resolution: Done
    • WT2.4.1
    • Affects Version/s: None
    • Component/s: None
    • Labels:

      Test/format reported the following failure:

        29: file, variable-length column-store
      t: session.verify: file:wt: post-ops verify: Device or resource busy
      

      The configuration that triggered the failure is:

      ############################################
      #  RUN PARAMETERS
      ############################################
      auto_throttle=1
      firstfit=0
      bitcnt=1
      bloom=1
      bloom_bit_count=7
      bloom_hash_count=10
      bloom_oldest=0
      cache=3
      checkpoints=1
      checksum=uncompressed
      chunk_size=6
      compaction=1
      compression=none
      data_extend=0
      data_source=file
      delete_pct=0
      dictionary=0
      evict_max=1
      file_type=row-store
      backups=1
      huffman_key=0
      huffman_value=0
      insert_pct=20
      internal_key_truncation=0
      internal_page_max=13
      isolation=random
      key_gap=10
      key_max=82
      key_min=24
      leak_memory=0
      leaf_page_max=17
      logging=0
      lsm_worker_threads=3
      merge_max=8
      mmap=1
      ops=100000
      prefix_compression=1
      prefix_compression_min=7
      repeat_data_pct=87
      reverse=0
      rows=100000
      runs=100
      split_pct=42
      statistics=0
      threads=1
      value_max=3167
      value_min=16
      wiredtiger_config=
      write_pct=24
      ############################################
      

      The test failure can be seen: http://build.wiredtiger.com:8080/job/wiredtiger-test-format-stress/5602/

            Assignee:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: