[SERVER-33021] Server started up using different collection wt files Created: 30/Jan/18  Updated: 21/Mar/18  Resolved: 31/Jan/18

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: 3.6.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Luigi Maestrelli Assignee: Mark Agarunov
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File WiredTiger     File WiredTiger.turtle     File WiredTiger.wt     Text File mongodb.log     File repair-SERVER-33021-2.tar.gz     File repair-SERVER-33021.tar.gz    
Issue Links:
Related
Operating System: ALL
Participants:

 Description   

Under the collection folder, I had 5 wt files for my collection.
For some reason, the server created another 5 files and started to use them.

For exemple, now I have collection-10-2456006026897874487.wt with 77MB and collection-10-4298854520594963500.wt with 2GB.

And I can't access the data from collection-10-4298854520594963500.wt

Even the collection "local" has this duplicated files. collection-0-2456006026897874487.wt and collection-0-4298854520594963500.wt

On the server log, I found just a "SERVER RESTARTED" on the day that the new wt files were created.

What can I do to recovery my data?



 Comments   
Comment by Luigi Maestrelli [ 01/Feb/18 ]

Hi,

Thank for all the help.
Is there a way to open the wt collection files and try to recovery at least some data?
Read the file in some raw form?

Thanks.

Comment by Mark Agarunov [ 31/Jan/18 ]

Hello lgmaestrelli,

Unfortunately, this behavior indicates that there was corruption on the disk, most often cause by a faulty storage layer. 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.

Thanks,
Mark

Comment by Luigi Maestrelli [ 31/Jan/18 ]

Hi.

That did not solved.
I can only access a few documents, and not the full collection.

Comment by Mark Agarunov [ 31/Jan/18 ]

Hello lgmaestrelli,

I've attached a repair attempt with the new files you've provided. Please let me know if this fixes the issue.

Thanks,
Mark

Comment by Luigi Maestrelli [ 31/Jan/18 ]

Hello.

After replacing the files I got a checksum error.
I'm attaching the log from the server startup.
Perhaps I sent you the wrong WiredTiger files. I previous attached the file from my machine and not the original files from the server. Sorry.
I will remove the old files and upload the new ones.

Thank you.

Comment by Mark Agarunov [ 30/Jan/18 ]

Hello lgmaestrelli,

Thank you for your report. I've attached a repair attempt of the files you provided. Please extract these files and replace them in your $dbpath and let us know if it resolves the issue. If you are still seeing errors after replacing these files, please provide the complete logs from the affected node(s) so that we can further investigate.

Thanks,
Mark

Generated at Thu Feb 08 04:32:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.