[SERVER-30419] WireTiger read checksum error Created: 30/Jul/17  Updated: 27/Jul/18  Resolved: 02/Aug/17

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

Type: Bug Priority: Major - P3
Reporter: Bing Zou Assignee: Mark Agarunov
Resolution: Done Votes: 0
Labels: envns, rns, rps, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File SERVER-30419-repair.tar.gz     File WiredTiger.turtle     File WiredTiger.wt    
Operating System: Linux
Participants:

 Description   

2017-07-30T02:49:11.254+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=2690fba6587a
2017-07-30T02:49:11.254+0000 I CONTROL [initandlisten] db version v3.4.1
2017-07-30T02:49:11.254+0000 I CONTROL [initandlisten] git version: 5e103c4f5583e2566a45d740225dc250baacfbd7
2017-07-30T02:49:11.254+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1t 3 May 2016
2017-07-30T02:49:11.254+0000 I CONTROL [initandlisten] allocator: tcmalloc
2017-07-30T02:49:11.254+0000 I CONTROL [initandlisten] modules: none
2017-07-30T02:49:11.254+0000 I CONTROL [initandlisten] build environment:
2017-07-30T02:49:11.254+0000 I CONTROL [initandlisten] distmod: debian81
2017-07-30T02:49:11.254+0000 I CONTROL [initandlisten] distarch: x86_64
2017-07-30T02:49:11.254+0000 I CONTROL [initandlisten] target_arch: x86_64
2017-07-30T02:49:11.255+0000 I CONTROL [initandlisten] options: { storage:

{ engine: "wiredTiger" }

}
2017-07-30T02:49:11.265+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=487M,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-07-30T02:49:11.278+0000 E STORAGE [initandlisten] WiredTiger error (0) [1501382951:278960][1:0x7f9299938cc0], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 167936: block header checksum of 1865166909 doesn't match expected checksum of 651691813
2017-07-30T02:49:11.279+0000 E STORAGE [initandlisten] WiredTiger error (0) [1501382951:279013][1:0x7f9299938cc0], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value
2017-07-30T02:49:11.279+0000 E STORAGE [initandlisten] WiredTiger error (-31804) [1501382951:279020][1:0x7f9299938cc0], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
2017-07-30T02:49:11.279+0000 I - [initandlisten] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 361
2017-07-30T02:49:11.279+0000 I - [initandlisten]



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

Hello xigua,

Thanks for your response. I'm glad to hear that this fixed the issue and everything is working again. To prevent this type of problem in the future, we recommend implementing regular backups and/or replication to mitigate any issues related to unreliable storage layers or server failures.

Thanks,
Mark

Comment by Bing Zou [ 02/Aug/17 ]

it's back. Thanks a lot.

Comment by Mark Agarunov [ 01/Aug/17 ]

Hello xigua,

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

Comment by Bing Zou [ 01/Aug/17 ]

As attached. Thanks.

Comment by Mark Agarunov [ 31/Jul/17 ]

Hello xigua,

Thank you for the report. Would you please upload the WiredTiger.wt and WiredTiger.turtle files so we can attempt a repair?

Thanks,
Mark

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