[SERVER-28364] WiredTiger file corrupted after server crash Created: 17/Mar/17 Updated: 27/Jul/18 Resolved: 20/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrea Ghelfi | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rpo, rpu, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
I am running a standalone mongodb server 3.2.6 on Suse 11 x86_64 (production system) {{2017-03-17T10:23:57.850+0100 E STORAGE [initandlisten] WiredTiger (-31802) [1489742637:850794][5845:0x7ffc3af69c80], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error I try to repair using mongod --repair with no success. |
| Comments |
| Comment by Mark Agarunov [ 20/Mar/17 ] |
|
Hello a_ghelfi, Unfortunately, this error indicates that the data became corrupted in some way. I would recommend a clean resync from a node that is not affected or restoring from a backup if possible. Thanks, |
| Comment by Andrea Ghelfi [ 17/Mar/17 ] |
|
Hello Mark, 2017-03-17T22:22:03.429+0100 W STORAGE [initandlisten] Recovering data from the last clean checkpoint. ***aborting after fassert() failure Thanks, |
| Comment by Mark Agarunov [ 17/Mar/17 ] |
|
Hello a_ghelfi, Thank you for the report. I've attached a repair attempt of the files you've provided. Would you please extract these files and replace them in your $dbpath and let us know if it resolves the issue? Thanks, |