[SERVER-39027] WiredTiger (-31802) [1547647803:509217][29607:0x7f20a0ab6cc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error Created: 16/Jan/19  Updated: 19/Feb/19  Resolved: 19/Feb/19

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

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

Issue Links:
Duplicate
is duplicated by SERVER-39028 WiredTiger (-31802) [1547647803:50921... Closed
Related
is related to WT-4554 Enhance WT salvage to handle the case... Closed
Participants:

 Description   

[root@ZhiJiao-B mongo]# mongod --dbpath /DATA/gttt/mongo/db --repair
2019-01-16T22:10:03.484+0800 I CONTROL [initandlisten] MongoDB starting : pid=29607 port=27017 dbpath=/DATA/gttt/mongo/db 64-bit host=ZhiJiao-B
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] db version v3.2.10
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] git version: 79d9b3ab5ce20f51c272b4411202710a082d0317
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] allocator: tcmalloc
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] modules: none
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] build environment:
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] distarch: x86_64
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] target_arch: x86_64
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] options: { repair: true, storage:

{ dbPath: "/DATA/gttt/mongo/db" }

}
2019-01-16T22:10:03.499+0800 I - [initandlisten] Detected data files in /DATA/gttt/mongo/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-01-16T22:10:03.499+0800 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint.
2019-01-16T22:10:03.499+0800 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=18G,session_max=20000,eviction=(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-01-16T22:10:03.509+0800 E STORAGE [initandlisten] WiredTiger (-31802) [1547647803:509217][29607:0x7f20a0ab6cc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2019-01-16T22:10:03.509+0800 E STORAGE [initandlisten] WiredTiger (0) [1547647803:509278][29607:0x7f20a0ab6cc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2019-01-16T22:10:03.509+0800 E STORAGE [initandlisten] WiredTiger (0) [1547647803:509296][29607:0x7f20a0ab6cc0], 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-01-16T22:10:03.509+0800 E STORAGE [initandlisten] WiredTiger (0) [1547647803:509313][29607:0x7f20a0ab6cc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2019-01-16T22:10:03.509+0800 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
2019-01-16T22:10:03.509+0800 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2019-01-16T22:10:03.509+0800 I CONTROL [initandlisten] dbexit: rc: 100



 Comments   
Comment by Eric Sedor [ 19/Feb/19 ]

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Comment by Eric Sedor [ 05/Feb/19 ]

Hi, if this is still an issue for you, would you please attach both the WiredTiger.wt and the WiredTiger.turtle files to this ticket or let us know if a secure upload is necessary? Thank you!

Comment by Eric Sedor [ 16/Jan/19 ]

This error during repairing typically indicates file- or disk-level corruption. While MongoDB 3.2 reached end of life on September 2018, we can provide limited assistance with this issue if this is your only copy of this data, and if the corruption is isolated to the WiredTiger.wt file.

Can you attach both the WiredTiger.wt and the WiredTiger.turtle files to this ticket? If you'd prefer not to do so publicly we can provide a secure upload portal. Just let us know.

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