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

Test/format seeing EBUSY return in verify

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Resolution: Fixed
    • None
    • WT2.5.2
    • None

    Description

      There was a Jenkins test failure over night:
      http://build.wiredtiger.com:8080/job/wiredtiger-test-format-stress-sanitizer/2529/console

      The interesting output is:

      t: session.verify: file:wt: post-ops verify: Device or resource busy

      The particular config is:

      ############################################
      		 
      #  RUN PARAMETERS
      		 
      ############################################
      		 
      auto_throttle=1
      		 
      firstfit=0
      		 
      bitcnt=3
      		 
      bloom=0
      		 
      bloom_bit_count=21
      		 
      bloom_hash_count=31
      		 
      bloom_oldest=0
      		 
      cache=1
      		 
      checkpoints=1
      		 
      checksum=uncompressed
      		 
      chunk_size=6
      		 
      compaction=1
      		 
      compression=zlib
      		 
      data_extend=0
      		 
      data_source=file
      		 
      delete_pct=12
      		 
      dictionary=0
      		 
      evict_max=5
      		 
      file_type=variable-length column-store
      		 
      backups=0
      		 
      huffman_key=0
      		 
      huffman_value=0
      		 
      insert_pct=8
      		 
      internal_key_truncation=1
      		 
      internal_page_max=14
      		 
      isolation=read-committed
      		 
      key_gap=20
      		 
      key_max=39
      		 
      key_min=28
      		 
      leak_memory=0
      		 
      leaf_page_max=17
      		 
      logging=0
      		 
      lsm_worker_threads=4
      		 
      merge_max=8
      		 
      mmap=1
      		 
      ops=100000
      		 
      prefix_compression=1
      		 
      prefix_compression_min=8
      		 
      repeat_data_pct=64
      		 
      reverse=0
      		 
      rows=100000
      		 
      runs=1
      		 
      split_pct=57
      		 
      statistics=0
      		 
      threads=1
      		 
      timer=0
      		 
      value_max=268
      		 
      value_min=16
      		 
      wiredtiger_config=
      		 
      write_pct=57
      		 
      ############################################

      The console goes on to report memory leaks from Berkeley DB, but I suspect that is a result of exiting aggressively.

      Attachments

        Issue Links

          is related to

          Task - A task that needs to be done. WT-1508 Avoid EBUSY returns to verify and salvage caused by checkpoints

          • Closed

          Task - A task that needs to be done. WT-1599 Grab the table list lock while building the list of handles to checkpoint

          • Closed

          Task - A task that needs to be done. WT-1705 Fix a bug in checkpoint, where it could get an EBUSY return.

          • Closed

          Task - A task that needs to be done. WT-1780 Update the session get btree busy check:

          • Closed
          related to

          Task - A task that needs to be done. WT-1 placeholder WT-1

          • Closed

          Task - A task that needs to be done. WT-2 What does metadata look like?

          • Closed

          Task - A task that needs to be done. WT-3 What file formats are required?

          • Closed

          Task - A task that needs to be done. WT-4 Flexible cursor traversals

          • Closed

          Task - A task that needs to be done. WT-5 How does pget work: is it necessary?

          • Closed

          Task - A task that needs to be done. WT-6 Complex schema example

          • Closed

          Task - A task that needs to be done. WT-7 Do we need the handle->err/errx methods?

          • Closed

          Task - A task that needs to be done. WT-8 Do we need table load, bulk-load and/or dump methods?

          • Closed

          Task - A task that needs to be done. WT-9 Does adding schema need to be transactional?

          • Closed

          Task - A task that needs to be done. WT-10 Basic "getting started" tutorial

          • Closed

          Task - A task that needs to be done. WT-11 placeholder #11

          • Closed

          Task - A task that needs to be done. WT-12 Write more examples

          • Closed

          Task - A task that needs to be done. WT-1483 dhandle session_inuse assertion failure

          • Closed

          Task - A task that needs to be done. WT-1643 EBUSY from truncate()

          • Closed

          Task - A task that needs to be done. WT-1735 When skipping a dirty page during a checkpoint, make sure the tree is marked dirty

          • Closed

          Task - A task that needs to be done. WT-1767 If the session-level attempt to lock a handle gets EBUSY, fall back to the slow path

          • Closed

          Activity

            People

              alexander.gorrod@mongodb.com Alexander Gorrod
              alexander.gorrod@mongodb.com Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: