[SERVER-29976] I have a Linux Centos 7 server, with an LVM configuration and a file system in XFS. Here you have a mongo 3.0.7 Created: 05/Jul/17  Updated: 06/Aug/18  Resolved: 02/Aug/17

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

Type: Bug Priority: Major - P3
Reporter: Carlos Cornel Assignee: Mark Agarunov
Resolution: Done Votes: 0
Labels: envm, rpo, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File DB&Log.rar     Text File Questions.txt     File SERVER-29976-repair.tar.gz     File WiredTiger.turtle     File WiredTiger.wt    
Operating System: Linux
Participants:

 Description   

Hi

After an unexpected shutdown a few days ago. Sends an error “***aborting after fassert() failure “. A new server with the same version was installed and the files of the corrupted database were placed, and after WT tools were used and where the file checksum presents problems, specfied in wiredtiger.wt

Thanks, Regards



 Comments   
Comment by Mark Agarunov [ 02/Aug/17 ]

Hello ccornel,

Thank you for providing the additional information. Unfortunately, this error indicates that the disk corruption affected more than just the WiredTiger.wt file. In this situation, I would recommend checking the integrity of your disks and then restoring from a backup.

Thanks,
Mark

Comment by Carlos Cornel [ 06/Jul/17 ]

Hello Mark Agarunov,

thank you so much for your quick response. The files attached in SERVER-29976-repair.tar.gz were replaced and the error related to the checksum was fixed, but, when i run the – repair command again, a new error appeared (described in the mongolog2.txt file). I attached the mongo database folder version 3.0.7 ( DB&log.tar). and the answers to the questionnaire. I really appreciate your help and interest.

Regards
Carlos Cornel

Comment by Mark Agarunov [ 05/Jul/17 ]

Hello ccornel,

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? If you are still seeing errors after replacing these files, please provide the complete logs from mongod so that we can further investigate. Additionally, if this issue persists, please provide the following information:

  1. What kind of underlying storage mechanism are you using? Are the storage devices attached locally or over the network? Are the disks SSDs or HDDs? What kind of RAID and/or volume management system are you using?
  2. Would you please check the integrity of your disks?
  3. Has the database always been running this version of MongoDB? If not please describe the upgrade/downgrade cycles the database has been through.
  4. Have you manipulated (copied or moved) the underlying database files? If so, was mongod running?
  5. Have you ever restored this instance from backups?
  6. What method do you use to create backups?
  7. When was the underlying filesystem last checked and is it currently marked clean?

Thanks,
Mark

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