[SERVER-32379] Need help with WiredTiger error after mongodb was stopped by system when there was no disk space. Created: 18/Dec/17  Updated: 27/Jul/18  Resolved: 19/Dec/17

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

Type: Bug Priority: Major - P3
Reporter: Eson Chen [X] Assignee: Mark Agarunov
Resolution: Done Votes: 0
Labels: envns, rdi, rps, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File WiredTiger.turtle     File WiredTiger.wt     File repair-SERVER-32379.tar.gz    
Operating System: ALL
Participants:

 Description   

I ran across a known bug and got my data file corrupted.

Mongodb was stopped by system because there was no disk space.

Mongodb is not able to start again.

WiredTiger (0) [1513560957:865590][3924:0x7fd6ee2b5700], file:index-23-4806698822797721925.wt, WT_SESSION.open_cursor: read checksum error for 32768B block at offset 430252032: block header checksum of 2902892101 doesn't match expected checksum of 3289519194

WiredTiger (0) [1513560957:865624][3924:0x7fd6ee2b5700], file:index-23-4806698822797721925.wt, WT_SESSION.open_cursor: index-23-4806698822797721925.wt: encountered an illegal file format or internal value

WiredTiger (-31804) [1513560957:865629][3924:0x7fd6ee2b5700], file:index-23-4806698822797721925.wt, WT_SESSION.open_cursor: the process must exit and restart: WT_PANIC: WiredTiger library panic

I was wondering if anyone is able to help me fix the file?



 Comments   
Comment by Mark Agarunov [ 19/Dec/17 ]

Hello Eson,

Thanks for your response. I'm glad to hear that this fixed the issue and everything is working again. To prevent this type of problem in the future please take note of the following guidelines to help mitigate any issues related to unreliable storage layers or server failures.

Thanks,
Mark

Comment by Eson Chen [X] [ 19/Dec/17 ]

I replaced the files, then Mongodb started to work again. Everything looks perfect. Thanks a lot.

Comment by Mark Agarunov [ 18/Dec/17 ]

Hello Eson,

Thank you for your report. I've attached a repair attempt of the files you provided. Please extract these files and replace them in your $dbpath and let us know if it resolves the issue. If you are still seeing errors after replacing these files, please provide the complete logs from the affected node(s) so that we can further investigate.

Thanks,
Mark

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