-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: WT2.6.1
-
Component/s: None
-
None
Hi!
It seems we got broken DB after our application crashed.
When trying to dump table using wt utility:
$ tar xzf broken-db.tar.gz $ ~/src/wiredtiger-2.6.1/wt -h . -C 'log=(enabled,recover=on),extensions=(/home/sbn/src/wiredtiger-2.6.1/ext/compressors/snappy/.libs/libwiredtiger_snappy.so)' list colgroup:main file:main.wt table:main $ ~/src/wiredtiger-2.6.1/wt -h . -C 'log=(enabled,recover=on),extensions=(/home/sbn/src/wiredtiger-2.6.1/ext/compressors/snappy/.libs/libwiredtiger_snappy.so)' dump main WiredTiger Dump (WiredTiger Version 2.6.1) Format=print Header table:main allocation_size=4KB,app_metadata=,block_allocation=best,block_compressor=,cache_resident=0,checksum=uncompressed,colgroups=,collator=,columns=(k,v),dictionary=0,encryption=(keyid=,name=),exclusive=0,extractor=,format=btree,huffman_key=,huffman_value=,immutable=0,internal_item_max=0,internal_key_max=0,internal_key_truncate=,internal_page_max=4KB,key_format=u,key_gap=10,leaf_item_max=0,leaf_key_max=0,leaf_page_max=32KB,leaf_value_max=0,log=(enabled=),lsm=(auto_throttle=,bloom=,bloom_bit_count=16,bloom_config=,bloom_hash_count=8,bloom_oldest=0,chunk_count_limit=0,chunk_max=5GB,chunk_size=10MB,merge_max=15,merge_min=0),memory_page_max=5MB,os_cache_dirty_max=0,os_cache_max=0,prefix_compression=0,prefix_compression_min=4,source=,split_deepen_min_child=0,split_deepen_per_child=0,split_pct=75,type=file,value_format=u Data [1449669479:483878][7809:0x7feb041fb720], file:main.wt, WT_SESSION.open_cursor: main.wt read error: failed to read 4096 bytes at offset 65536: WT_ERROR: non-specific WiredTiger error lt-wt: cursor open(table:main) failed: WT_ERROR: non-specific WiredTiger error Segmentation fault (core dumped)
File main.wt is only 4KiB in size.
Do you have any ideas how this could happen?
Maybe some already known problem?
Tarball with broken DB attached.
Thanks!