[SERVER-34534] file:WiredTiger.wt, connection: read checksum error Created: 18/Apr/18  Updated: 27/Jul/18  Resolved: 21/Jun/18

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

Type: Bug Priority: Major - P3
Reporter: Michael Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: envns, rdi, rpns, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2012 R2


Attachments: File WiredTiger.turtle     File WiredTiger.wt     File repair_attempt.tar.gz    
Operating System: Windows
Participants:

 Description   

I'm not able to access my mongo db with the following error in the logs. The disk space on the server became full and now Mongo won't allow connections and the service runs only for a short time before stopping. The disk space has been cleared but I have been reading around and it could be the wiredtiger files have been corrupted.

I have attached these. Are they able to be repaired?

2018-04-18T13:34:10.146+0100 I CONTROL  [main] ***** SERVER RESTARTED *****
2018-04-18T13:34:10.171+0100 I CONTROL  [initandlisten] MongoDB starting : pid=38272 port=27017 dbpath=D:\Scientis\Data 64-bit host=WINDOWS-QQUTJK2
2018-04-18T13:34:10.171+0100 I CONTROL  [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
2018-04-18T13:34:10.171+0100 I CONTROL  [initandlisten] db version v3.2.1
2018-04-18T13:34:10.172+0100 I CONTROL  [initandlisten] git version: a14d55980c2cdc565d4704a7e3ad37e4e535c1b2
2018-04-18T13:34:10.172+0100 I CONTROL  [initandlisten] allocator: tcmalloc
2018-04-18T13:34:10.172+0100 I CONTROL  [initandlisten] modules: none
2018-04-18T13:34:10.172+0100 I CONTROL  [initandlisten] build environment:
2018-04-18T13:34:10.172+0100 I CONTROL  [initandlisten]     distmod: 2008plus
2018-04-18T13:34:10.172+0100 I CONTROL  [initandlisten]     distarch: x86_64
2018-04-18T13:34:10.172+0100 I CONTROL  [initandlisten]     target_arch: x86_64
2018-04-18T13:34:10.172+0100 I CONTROL  [initandlisten] options: { config: "C:\Program Files\Scientis\APM_Mongo\etc\Mongo.yaml ", storage: { dbPath: "D:\Scientis\Data", directoryPerDB: true, journal: { enabled: false } }, systemLog: { destination: "file", logAppend: true, path: "C:\Program Files\Scientis\APM_Mongo\logs\mongo.log" } }
2018-04-18T13:34:10.173+0100 I -        [initandlisten] Detected data files in D:\Scientis\Data created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-04-18T13:34:10.173+0100 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=114G,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),,log=(enabled=false),
2018-04-18T13:34:10.197+0100 E STORAGE  [initandlisten] WiredTiger (0) [1524054850:197391][38272:140720579154768], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 24576: block header checksum of 2682627311 doesn't match expected checksum of 3735279951
2018-04-18T13:34:10.197+0100 E STORAGE  [initandlisten] WiredTiger (0) [1524054850:197391][38272:140720579154768], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value
2018-04-18T13:34:10.197+0100 E STORAGE  [initandlisten] WiredTiger (-31804) [1524054850:197391][38272:140720579154768], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
2018-04-18T13:34:10.197+0100 I -        [initandlisten] Fatal Assertion 28558
2018-04-18T13:34:10.197+0100 I -        [initandlisten] 
 
***aborting after fassert() failure



 Comments   
Comment by Kelsey Schubert [ 18/Apr/18 ]

Hi mclass,

Thank you for your report. I've attached a repair attempt, repair_attempt.tar.gz, 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 so that we can further investigate.

Thank you,
Kelsey

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