[SERVER-32780] DB directory snapshot from hardware failure Created: 18/Jan/18 Updated: 21/Mar/18 Resolved: 16/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Langston | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Hi There, We have got snapshot mongodb directory from broken server hardware, when we are trying to start mongo
Then repair attempt deleting all our data
there is no replica server or working backup unfortunately I'm sharing files bellow any help would be really appreciated. Regards |
| Comments |
| Comment by Kelsey Schubert [ 16/Feb/18 ] |
|
Hi langston, 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 about your data files and we will reopen the ticket. Regards, |
| Comment by Kelsey Schubert [ 23/Jan/18 ] |
|
Hi langston, After reviewing the files, it appears that the _mdb_catalog.wt suffered from some form of os storage layer corruption. Unfortunately, during repair, this file is considered the authoritative list of collections and indexes stored by WiredTiger. Since these data files in the WT Catalog were not referenced by the corrupted _mdb_catalog.wt, the repair process dropped the files to free disk space taken up by data that could never be accessed. We're looking into modifying the behavior of --repair to not drop unknown idents, but either move them aside or preferably recreate catalog entries for them (in a lost+found database or such) and let the user explicitly delete them again if they're unwanted. In terms of data recovery, it is not possible at this time to determine whether only _mdb_catalog.wt was affected or if there is corruption on other files as well. If you have a backup prior to running the repair operation, we can attempt a manual repair using these files. If not, I would suggest taking a backup of your current files, and then run a filesystem recovery tool to recover the data files using a recovery software or service. If you're able to recover these files, please let us know so we can attempt to help repair this corruption. For us to attempt to manually recover data, we would need a complete directory listing of the $dbpath as well as information about options that were set when creating these collections. Additionally, would you please clarify when this mongod was always running 3.6.1? If the collections were created in on an earlier version, would you please specify and clarify whether the Feature Compatibility was upgraded to 3.6? If the size of your database is not unwieldly, I would be happy to provide a secure upload portal as it may be help us if you could provide your complete $dbpath, but I don't think it's necessary for us to proceed. Thank you, |
| Comment by Ramon Fernandez Marina [ 19/Jan/18 ] |
|
Sorry to hear you've run into issues langston, we're looking into this issue and the files you uploaded, and will post updates in this ticket as we have them. Regards, |