[SERVER-28820] Recovery failed: WT_NOTFOUND: item not found Created: 17/Apr/17 Updated: 06/Aug/18 Resolved: 10/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, WiredTiger |
| Affects Version/s: | 3.2.4 |
| Fix Version/s: | 3.5.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew | Assignee: | Susan LoVerso |
| Resolution: | Done | Votes: | 0 |
| Labels: | wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux, Ubuntu 14.04 64bit |
||
| Attachments: |
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | Linux |
| Steps To Reproduce: | run mongod |
| Participants: |
| Description |
|
My server broke down and all I had is copy of database files in /data/db. No proper mongodump, only files. |
| Comments |
| Comment by Andrew [ 11/Jul/17 ] |
|
Hi, Ramon, previously in my message: So my question is do you (or Alexander) still have these files? I need them urgently. |
| Comment by Ramon Fernandez Marina [ 10/Jul/17 ] |
|
kasperpro, I believe we only have whatever files are attached to this ticket, are those the files you're inquiring about? Thanks, |
| Comment by Andrew [ 10/Jul/17 ] |
|
Good afternoon, |
| Comment by Githook User [ 06/Jun/17 ] |
|
Author: {u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}Message: Import wiredtiger: 7aaeaaa054d1ac27a95c79984f7ca69ba739caae from branch mongodb-3.6 ref: 78109ca3fe..7aaeaaa054
|
| Comment by Githook User [ 25/Apr/17 ] |
|
Author: {u'username': u'sueloverso', u'name': u'sueloverso', u'email': u'sue@mongodb.com'}Message: |
| Comment by Andrew [ 22/Apr/17 ] |
|
Hello Sue LoVerso, Anyway, thank you so much! Now I am able to make mongodump and recover my data. |
| Comment by Susan LoVerso [ 20/Apr/17 ] |
|
Hello kasperpro. There is definitely a problem with the journal files. As my earlier comment implied, they're zeroed out or removed. Please investigate what may have happened there. I was able to get a mongod up and running on your data with the following steps:
|
| Comment by Susan LoVerso [ 20/Apr/17 ] |
|
The good news is that with your tarball, I can reproduce the error and investigate where exactly it is coming from. Thank you for uploading the information. |
| Comment by Susan LoVerso [ 20/Apr/17 ] |
|
Hello kasperpro, I have downloaded the tarball, you can deactivate the link. I will remove all files when this ticket is complete. Can you tell me about your journal directory? The journal files in the tarball are effectively empty. The first log file contains a few log records that are for system, internal information. All the rest of the log files are zeroed (WiredTiger will create a new log file on each restart attempt). The two error message screen shots show one restart with journal enabled and one without it. Did you switch back and forth with journal on/off? Is there any possibility that the journal directory is on a different file system and that directory could be shared with another mongod process? |
| Comment by Andrew [ 20/Apr/17 ] |
|
Alexander, please find database files copy. |
| Comment by Alexander Gorrod [ 18/Apr/17 ] |
|
In order to understand better what is happening we would need a tarball of your dbdir, including the journal files. Would you be willing to provide that? If so can you give us some indication about how much data is involved? |
| Comment by Andrew [ 18/Apr/17 ] |
|
Still getting error, please see in attachment - debug_error1. |
| Comment by Mark Agarunov [ 17/Apr/17 ] |
|
Hello kasperpro 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, |
| Comment by Andrew [ 17/Apr/17 ] |
|
BTW related with ticket |