[SERVER-38406] collection filename.wt does not appear to be a WiredTiger file Created: 05/Dec/18 Updated: 01/Feb/19 Resolved: 01/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.11 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Den Fomichev | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
after an VM clear shutdown we cannot start back mongodb with this error in log:
The outher ways to get data from this collection file and move them to outher mongo instance facing the same error: We try: 2) wt tool specially build for our wiretiger version (http://source.wiredtiger.com/2.9.2/command_line.html#util_salvage)
[1544005066:138304][28344:0x7fe82dc5c300], file:collection-2--2481999773037646866.wt, WT_SESSION.verify: collection-2--2481999773037646866.wt does not appear to be a WiredTiger file: WT_ERROR: non-specific WiredTiger error
[1544005420:773648][29867:0x7f8a8dbe0300], file:collection-2--2481999773037646866.wt, WT_SESSION.salvage: collection-2--2481999773037646866.wt does not appear to be a WiredTiger file: WT_ERROR: non-specific WiredTiger error With the help of wt utility (salvage -> dump -> load) we recover some outher collection files to use in outher mongo instance but not this one Is there some outher way to fix this or just extract data from it? What additional data (files or so) you need to clarify the problem (The size of problem collection filesis close to 200Gb.)? |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 06/Dec/18 ] |
|
Hello Den, I'm sorry, I should have been more clear. Unfortunately, it is likely that the file is unrecoverable. You may be able to start the node again with by replacing the WiredTiger.wt and WiredTiger.turtle files with repair_attempt.tar In this situation, our best recommendation would be to resync the affected node or restore from a backup if possible. 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.
For further MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. Users there may have an unofficial method of recovering the data. Thank you, Danny |
| Comment by Den Fomichev [ 06/Dec/18 ] |
|
> If you attach your WiredTiger.wt and WiredTiger.turtle files to this ticket, I can attempt a recovery using an internal tool. Requested files are added to the ticket. You need full collection file to attempt a recovery (~200Gb) yourself or You will supply us with the instructions to try it ourselves? Tank You for Your effort. |
| Comment by Danny Hatcher (Inactive) [ 05/Dec/18 ] |
|
Hello Den, If you attach your WiredTiger.wt and WiredTiger.turtle files to this ticket, I can attempt a recovery using an internal tool. However, if that does not work then the only other recourse would be for you to restore from a backup or perform an initial sync from a healthy replica set node. Thank you, Danny |