[SERVER-44271] [Data recovery] WiredTiger.turtle: fatal turtle file read error: WT_NOTFOUND: item not found Created: 26/Oct/19 Updated: 20/Dec/19 Resolved: 20/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 4.0.13 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Marcin W | Assignee: | Carl Champain (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
Hi, I had a hard drive failure, managed to recover files, but it seems like there's still an issue with them. I'm getting an error: WiredTiger.turtle: fatal turtle file read error: WT_NOTFOUND: item not found
In total my DB files are 40MB, so I can upload them if needed, but not sure if it'll help, just in case I've attached tree of files that R-Studio managed to recover. Please, help me... how can I recover my database? At least some of it... it's impossible to recover this data by other means, so I would really appropriate help |
| Comments |
| Comment by Carl Champain (Inactive) [ 20/Dec/19 ] | ||||||||
|
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. Thank you, | ||||||||
| Comment by Carl Champain (Inactive) [ 04/Dec/19 ] | ||||||||
|
Any updates on this issue? | ||||||||
| Comment by Louis Williams [ 08/Nov/19 ] | ||||||||
|
The --repair orphan recovery process attemtps to locate .wt data files on disk that are in the MongoDB collection catalog, but are missing from the WT metadata. This implies that corrupt WT metadata lost knowledge of a data file. We can look for the data file because a higher-level of MongoDB knows the data file might exist, hence the "orphan" terminology. The error message "Orphan file recovery is not supported on Windows" was added because the procedure involves moving files while the directory is open by the process, and Windows filesystem permissions made this more effort than we were willing to put in for a best-effort data recovery procedure. Regarding the error on Linux, I found this blog post on Google that suggests the fdatasync issue is a result of mounting a Windows filesystem through your Ubuntu VM. marcin_wo_wroc@o2.pl did you make a backup of your database before running --repair? The log message "Collection TSMA.GeoLocation dropped: Orphan file recovery is not supported on Windows" indicates that MongoDB deleted the metadata for that collection, but not the data file. However, running --repair again will still not be able to recover the orphan because the metadata has been lost. Please report back if you can re-run repair on the original, corrupt data files on a non-shared data directory on a Linux filesystem. | ||||||||
| Comment by Marcin W [ 06/Nov/19 ] | ||||||||
|
Somehow I cannot make repair feature work on linux. I have MongoDB version 4.0.13 on both: Windows and Linux (Ubuntu) I've setup configs of both to run with data in the same directory. After that I cleaned up data (removed current, unpacked my damaged database into the directory), and run the repair. See }}{{fail_windows.txt After that I did the clean up, logged into Ubuntu and run repair on Mongo out there. See }}{{fail_linux.txt possibly the key part:
@Carl - "Are you using a replica set?" - no, I am not.
| ||||||||
| Comment by Marcin W [ 01/Nov/19 ] | ||||||||
|
Just a quick update: sadly the linux version I have is 4.2, while my files are from 4.0, so it doesn't even detect collections correctly. I won't be able to get back to the topic till after the weekend, but please, don't close the ticket yet. Thank you.
| ||||||||
| Comment by Marcin W [ 28/Oct/19 ] | ||||||||
|
Oh, thanks! I totally forgot about the repair option! It can see all my collections in the log, which is superb news, but it throws an "Orphan file recovery is not supported on Windows"
I'll try to get ubuntu up and running and attempt to restore it from there. Will report back ASAP (likely tomorrow). | ||||||||
| Comment by Carl Champain (Inactive) [ 28/Oct/19 ] | ||||||||
|
Thanks for the report. A couple of questions: |