[SERVER-35942] WiredTiger won't recognized collections Created: 02/Jul/18  Updated: 14/Aug/18  Resolved: 02/Jul/18

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: 3.6.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Ubirata Bezerra Assignee: Nick Brewer
Resolution: Done Votes: 0
Labels: envm, rge, rpu, trct, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 9.0 with Graylog 2.4.5 and elasticsearch 5.6.10


Attachments: HTML File WiredTiger     File WiredTiger.turtle     File WiredTiger.wt     File WiredTigerLAS.wt     File mongodb-backup.tar.bz2     File sizeStorer.wt    
Operating System: Linux
Participants:

 Description   

Dears,

A few days ago, when I ran a VM snapshot, My VM crashed with Graylog application. Other packages and configurations has still OK, but the MongoDB doesn't.

When I run command to start mongoDB, I have this error:

  1. sudo -u mongod -s
  2. mongod --dbpath /srv/data/mongo

This is result:

2018-06-28T15:22:47.718-0300 I - [initandlisten] Detected data files in /srv/data/mongodb created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-06-28T15:22:47.718-0300 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=3429M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),cache_cursors=false,log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2018-06-28T15:22:48.534-0300 E STORAGE [initandlisten] WiredTiger error (0) [1530210168:534752][8076:0x7f8566148580], file:WiredTiger.wt, connection: WiredTiger.turtle: encountered an illegal file format or internal value: (__wt_turtle_read, 291)
2018-06-28T15:22:48.534-0300 E STORAGE [initandlisten] WiredTiger error (-31804) [1530210168:534841][8076:0x7f8566148580], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
2018-06-28T15:22:48.534-0300 F - [initandlisten] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 366
2018-06-28T15:22:48.534-0300 F - [initandlisten]

***aborting after fassert() failure



 Comments   
Comment by Nick Brewer [ 02/Jul/18 ]

Hi usbezerra

It looks like the WiredTiger.turtle file you've uploaded is badly corrupted - this file contains the metadata that is used to interpret WiredTiger.wt, which is in turn used to interpret all other .wt files. With that file in its current state, any repair attempts we make are going to be unsuccessful.

In this situation, our best recommendation would be to resync the affected node if it is a replica set member, or restore from a backup if one is available.

Some guidelines for avoiding issues related to unreliable storage layers or server failures:

Regards,
Nick

Comment by Ubirata Bezerra [ 02/Jul/18 ]

i'd like to start recover this database, or help to reach it. If doesn't, i'd like to read theses collections or export them to another server already started.
Tks a lot

Generated at Thu Feb 08 04:41:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.