[SERVER-25998] journal/WiredTigerLog.0000000222 corrupted Created: 07/Sep/16 Updated: 14/Aug/18 Resolved: 08/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ashley Mort | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rpo, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | Linux |
| Steps To Reproduce: | happens whenever I try to start mongodb |
| Participants: |
| Description |
|
Power failure on server now getting this error when I try to start. Repair operation fails. 2016-09-07T15:19:25.542+0000 E STORAGE [initandlisten] WiredTiger (-31802) [1473261565:542419][19988:0x7fba68a4fd40], txn-recover: log file journal/WiredTigerLog.0000000222 corrupted: Bad magic number 740455270: WT_ERROR: non-specific WiredTiger error |
| Comments |
| Comment by Kelsey Schubert [ 08/Sep/16 ] |
|
Hi mortac8, I'm glad that deleting the subsequent log files resolved the issue. Since this issue appears to be the result of a filesystem bug, I am going to close this ticket. It is worth noting that the data in the corrupted file is not compressed. If you are using the default compression settings, WiredTiger did not write the contents of this file. Non-default compression settings would be most likely specified in your configuration file. Kind regards, |
| Comment by Ashley Mort [ 08/Sep/16 ] |
|
Deleting all log files except 0021 seems to have resolved my issue. Thanks! |
| Comment by Ashley Mort [ 07/Sep/16 ] |
|
I believe I am using the default compression, snappy. I'm not positive how to confirm this. [root@sandbox journal]# ls -l |
| Comment by Kelsey Schubert [ 07/Sep/16 ] |
|
Hi mortac8, Thank you for uploading the corrupted file. Please note that I have removed the attachment from this ticket in case it contains sensitive data. Since the uploaded file contains data that is not written to WiredTiger log files, this issue appears to be the result of a filesystem bug following the power failure.
To continue to investigate your system, please answer the following questions:
To understand whether this log file was active when the power failure occurred, please provide the following information:
My recommendation would be to create a copy of your $dbpath and attempt to restart after deleting the corrupted file and all subsequent log files. Please note that if 222 was not the last active log file, removing these files will lose some data, so I would suggest that you first test this procedure on a copy. Kind regards, |