Operational Defect Database

BugZero found this defect 2436 days ago.

MongoDB | 398052

[SERVER-29848] file:WiredTiger.wt: corruption problem

Last update date:

10/3/2017

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

No fixed releases provided.

Description:

Info

We are running mongo:3.2.5 in docker I have a backup of an old database (made by simply copying all files in a backup folder). Now we need to restore that db. But running mongo docker fails. It says that file WiredTiger.wt is corrupted: 2017-06-26T07:03:56.203+0000 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2017-06-26T07:03:56.203+0000 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint. 2017-06-26T07:03:56.203+0000 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=74G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0), 2017-06-26T07:03:56.311+0000 E STORAGE [initandlisten] WiredTiger (-31802) [1498460636:311432][1:0x7f328e048c80], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error 2017-06-26T07:03:56.311+0000 E STORAGE [initandlisten] WiredTiger (0) [1498460636:311510][1:0x7f328e048c80], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata 2017-06-26T07:03:56.311+0000 E STORAGE [initandlisten] WiredTiger (0) [1498460636:311527][1:0x7f328e048c80], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk 2017-06-26T07:03:56.311+0000 E STORAGE [initandlisten] WiredTiger (0) [1498460636:311543][1:0x7f328e048c80], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options 2017-06-26T07:03:56.313+0000 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error 2017-06-26T07:03:56.362+0000 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating 2017-06-26T07:03:56.362+0000 I CONTROL [initandlisten] dbexit: rc: 100 How can I repair it?

Top User Comments

kdkavanagh commented on Tue, 3 Oct 2017 13:40:45 +0000: Hi @mark.agarunov, I'm suffering from a similar problem. Any suggestions on how to repair these files myself? skelter commented on Tue, 27 Jun 2017 13:09:07 +0000: Thanks, Mark! I uploaded repair files, database has started and now it's working! Problem is solved now. mark.agarunov commented on Mon, 26 Jun 2017 16:50:17 +0000: Hello skelter, 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: 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? Would you please check the integrity of your disks? Has the database always been running this version of MongoDB? If not please describe the upgrade/downgrade cycles the database has been through. Have you manipulated (copied or moved) the underlying database files? If so, was mongod running? Have you ever restored this instance from backups? What method do you use to create backups? When was the underlying filesystem last checked and is it currently marked clean? Thanks, Mark

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...