[SERVER-41323] WiredTiger error (-31802) Created: 26/May/19  Updated: 24/Jun/19  Resolved: 24/Jun/19

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

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

Attachments: File SERVER-41323_repair_attempt.tgz     HTML File WiredTiger     File WiredTiger.lock     File WiredTiger.turtle     File WiredTiger.wt     File WiredTigerLAS.wt     File _mdb_catalog.wt     File mongo.conf    
Issue Links:
Duplicate
is duplicated by SERVER-41325 WiredTiger.wt, connection: read check... Closed
Operating System: ALL
Participants:

 Description   

I only backup my whole mongo directory without stopping the mongod instance, after finishing the System initialization, I returned mongo directory and try "bin/mongod -f mongo.conf", it fails. Then I check the mongo.log and find out that these must be some corruption happened. I tried "repair" and it fails with the log bellow. I also tried WiredTiger tools and it fails with almost same err. please help me. Dataset here is very important for me .

2019-05-26T12:23:10.481+0800 I CONTROL  [main] ** WARNING: --rest is specified without --httpinterface,
2019-05-26T12:23:10.481+0800 I CONTROL  [main] **          enabling http interface
[root@iZbp13lmtcdw0hu47yyxmhZ mongodb]# vim mongo.log2019-05-26T12:23:10.507+0800 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2019-05-26T12:23:10.507+0800 I STORAGE  [initandlisten] Detected WT journal files.  Running recovery from last checkpoint.
2019-05-26T12:23:10.507+0800 I STORAGE  [initandlisten] journal to nojournal transition config: create,cache_size=1468M,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),
2019-05-26T12:23:10.561+0800 E STORAGE  [initandlisten] WiredTiger error (-31802) [1558844590:561589][9740:0x7f1a255a3ce0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2019-05-26T12:23:10.561+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1558844590:561652][9740:0x7f1a255a3ce0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2019-05-26T12:23:10.561+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1558844590:561663][9740:0x7f1a255a3ce0], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
2019-05-26T12:23:10.561+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1558844590:561673][9740:0x7f1a255a3ce0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2019-05-26T12:23:10.562+0800 I -        [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 253
2019-05-26T12:23:10.562+0800 I STORAGE  [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2019-05-26T12:23:10.562+0800 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2019-05-26T12:23:10.562+0800 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2019-05-26T12:23:10.562+0800 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2019-05-26T12:23:10.562+0800 I CONTROL  [initandlisten] now exiting
2019-05-26T12:23:10.562+0800 I CONTROL  [initandlisten] shutting down with code:100



 Comments   
Comment by Eric Sedor [ 24/Jun/19 ]

zhuangdanyang, we haven't heard from you in some time and are going to close this ticket. Hopefully the repair attempt helped!

Comment by Eric Sedor [ 28/May/19 ]

Based on what you have said and on additional details provided in SERVER-41325, we believe your suspicion is correct and that the problem is that the backup was taken by copying files from a running instance.

We have performed a repair attempt on the WiredTiger.turtle and WiredTiger.wt files and provided them in SERVER-41323_repair_attempt.tgz.

Please keep in mind that this repair effort may not be successful, and consider a recommended backup method in the future.

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