[SERVER-46335] Unable to start mongo due corrupt WiredTiger Created: 23/Feb/20  Updated: 15/Sep/20  Resolved: 15/Sep/20

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

Type: Bug Priority: Major - P3
Reporter: Lucas Schiochet Assignee: Eric Sedor
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File WiredTiger.wt    
Operating System: ALL
Participants:

 Description   

The data is crucial and i cannot recover my data.

i looked others issues similars, and always you try to fix the file.

Please, can you guys fix?

 
2020-02-23T19:20:29.911+0000 I STORAGE  [initandlisten]
 
2020-02-23T19:20:29.911+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
 
2020-02-23T19:20:29.911+0000 I STORAGE  [initandlisten] **          See [http://dochub.mongodb.org/core/prodnotes-filesystem]
 
2020-02-23T19:20:29.911+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=1459M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress),
 
2020-02-23T19:20:29.922+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1582485629:922531][21427:0x7fe3540af180], [file:WiredTiger.wt|file:///WiredTiger.wt], connection: WiredTiger.turtle: encountered an illegal file format or internal value
 
2020-02-23T19:20:29.922+0000 E STORAGE  [initandlisten] WiredTiger error (-31804) [1582485629:922576][21427:0x7fe3540af180], [file:WiredTiger.wt|file:///WiredTiger.wt], connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
 
2020-02-23T19:20:29.922+0000 I -        [initandlisten] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 365
 
2020-02-23T19:20:29.922+0000 I -        [initandlisten]
 
  



 Comments   
Comment by Eric Sedor [ 15/Sep/20 ]

Hi,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved.

Sincerely,
Eric

Comment by Eric Sedor [ 21/Apr/20 ]

Hi lucas@becon.com.br, can you please let us know the results of a mongod --repair using MongoDB 4.2?

Comment by Eric Sedor [ 03/Mar/20 ]

Thanks lucas@becon.com.br;

3.4 reached end of life in January of 2020.

The ideal resolution for this issue is to perform a clean resync from an unaffected node. If you are not running a replica set deployment, we recommend doing so at the earliest opportunity.

For this case, can you please try using MongoDB 4.2 and running mongod --repair? Let us know if that does not help.

Gratefully,
Eric

Comment by Lucas Schiochet [ 25/Feb/20 ]

Mainly my server runs on db version v3.4.23.

But i try to recover in 3.6.1, 4.0 and 4.2 and the result was the same error on start.

i Believe that is a conflict between WIredTiger.wt with the collection-*.wt (in attachment)

Comment by Eric Sedor [ 24/Feb/20 ]

Hi lucas@becon.com.br,

Can you clarify the version of MongoDB you are seeing this error on?

Sincerely,
Eric

Comment by Lucas Schiochet [ 24/Feb/20 ]

All files (wt turtle lock etc) are available  are the zip (206 MB) [https://www.dropbox.com/s/4fbfk1acpt3f7tf/output_file.zip

I put this way because 150 mb limit|https://www.dropbox.com/s/4fbfk1acpt3f7tf/output_file.zip?dl=0]

Generated at Thu Feb 08 05:11:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.