[SERVER-38807] WiredTiger.wt is corrupt, repair needed (Fatal Assertion 28558) Created: 02/Jan/19  Updated: 28/Feb/19  Resolved: 28/Feb/19

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

Type: Bug Priority: Major - P3
Reporter: Brandon Baratono Assignee: Danny Hatcher (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

WiredTiger.wt is corrupt, as such the server will not start.  I have attached the files, how can these be repaired?

2019-01-02T12:02:07.429-0500 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=11G,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-02T12:02:07.436-0500 E STORAGE [initandlisten] WiredTiger (0) [1546448527:436160][16069:0x7fb6179c6dc0], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 24576: block header checksum of 802850087 doesn't match expected checksum of 3176529801
2019-01-02T12:02:07.436-0500 E STORAGE [initandlisten] WiredTiger (0) [1546448527:436194][16069:0x7fb6179c6dc0], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value
2019-01-02T12:02:07.436-0500 E STORAGE [initandlisten] WiredTiger (-31804) [1546448527:436205][16069:0x7fb6179c6dc0], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
2019-01-02T12:02:07.436-0500 I - [initandlisten] Fatal Assertion 28558
2019-01-02T12:02:07.436-0500 I - [initandlisten]

 

Thanks



 Comments   
Comment by Danny Hatcher (Inactive) [ 28/Feb/19 ]

Hello,

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.

Thanks,

Danny

Comment by Danny Hatcher (Inactive) [ 01/Feb/19 ]

Hello Brandon,

Was the above repair attempt successful?

Thank you,

Danny

Comment by Danny Hatcher (Inactive) [ 02/Jan/19 ]

Hi Brandon,

Thanks for the report, we have improved our repair functionality in MongoDB 4.0.3 (SERVER-19815), which should provide a resolve a number of issues that may occur due to a faulty disk layer and increase the chances of success since it acts on more files.

To proceed with the repair attempt, please follow these steps

  1. take a complete copy of your complete dbpath and set it aside
  2. download MongoDB 4.0.3 or newer
  3. start MongoDB 4.0.3 (or newer) with --repair pointing at your data files
  4. after the process completes, you may restart with your original binary

Please let me know if you have any questions about this process or run into any issues.

Thank you,
Danny

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