[SERVER-31833] WiredTiger.wt file corrupted after unclean shutdown, cannot recover Created: 05/Nov/17  Updated: 07/Jan/18  Resolved: 01/Dec/17

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

Type: Bug Priority: Major - P3
Reporter: Shubham Dogra Assignee: Mark Agarunov
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File WiredTiger     File WiredTiger.lock     File WiredTiger.turtle     File WiredTiger.wt     File WiredTigerLAS.wt     File repair-SERVER-31833.tar.gz    
Operating System: ALL
Participants:

 Description   

[root@linux75 mongo]# mongod --dbpath /var/lib/mongo
2017-11-05T07:55:25.387+0000 I CONTROL  [initandlisten] MongoDB starting : pid=30422 port=27017 dbpath=/var/lib/mongo 64-bit host=linux75
2017-11-05T07:55:25.387+0000 I CONTROL  [initandlisten] db version v3.2.1
2017-11-05T07:55:25.387+0000 I CONTROL  [initandlisten] git version: a14d55980c2cdc565d4704a7e3ad37e4e535c1b2
2017-11-05T07:55:25.387+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2017-11-05T07:55:25.387+0000 I CONTROL  [initandlisten] modules: none
2017-11-05T07:55:25.387+0000 I CONTROL  [initandlisten] build environment:
2017-11-05T07:55:25.387+0000 I CONTROL  [initandlisten]     distarch: x86_64
2017-11-05T07:55:25.387+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2017-11-05T07:55:25.387+0000 I CONTROL  [initandlisten] options: { storage: { dbPath: "/var/lib/mongo" } }
2017-11-05T07:55:25.478+0000 I -        [initandlisten] Detected data files in /var/lib/mongo created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2017-11-05T07:55:25.479+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=1G,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-11-05T07:55:25.484+0000 E STORAGE  [initandlisten] WiredTiger (-31802) [1509868525:484423][30422:0x7f248d85fcc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2017-11-05T07:55:25.484+0000 E STORAGE  [initandlisten] WiredTiger (0) [1509868525:484445][30422:0x7f248d85fcc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2017-11-05T07:55:25.484+0000 E STORAGE  [initandlisten] WiredTiger (0) [1509868525:484453][30422:0x7f248d85fcc0], 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-11-05T07:55:25.484+0000 E STORAGE  [initandlisten] WiredTiger (0) [1509868525:484466][30422:0x7f248d85fcc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2017-11-05T07:55:25.485+0000 I -        [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error
2017-11-05T07:55:25.485+0000 I STORAGE  [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2017-11-05T07:55:25.485+0000 I CONTROL  [initandlisten] dbexit:  rc: 100



 Comments   
Comment by Mark Agarunov [ 01/Dec/17 ]

Hello sitesholic,

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 and we will reopen the ticket.

Thanks,
Mark

Comment by Mark Agarunov [ 06/Nov/17 ]

Hello sitesholic,

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:28:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.