[SERVER-53851] WiredTiger error read checksum error Created: 16/Jan/21 Updated: 10/Feb/21 Resolved: 10/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergei Grigoriev | Assignee: | Edwin Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi. Service Mongod failed: 2021-01-16T07:25:59.101+0100 I - [conn772] Index Build: scanning collection: 61459500/76903785 79% 2021-01-16T07:26:01.403+0100 E STORAGE [conn772] WiredTiger error (0) [1610778361:383471][898:0x7efd59b97700], file:collection-1106--3373039797341136654.wt, WT_CURSOR.next: __wt_block_read_off, 274: collection-1106- -- Jan 16 07:26:01 Debian-102-buster-64-minimal systemd[1]: mongod.service: Main process exited, code=killed, status=6/ABRT --
|
| Comments |
| Comment by Edwin Zhou [ 10/Feb/21 ] |
|
Hi sergei_grigoriev@belkatechnologies.com, We're happy to hear you're able to start the server! Thanks for updating us on your situation. Best, |
| Comment by Sergei Grigoriev [ 10/Feb/21 ] |
|
Hi edwin.zhou. Thanks for the answer. Mongo after falling, started and runs without errors.
|
| Comment by Edwin Zhou [ 08/Feb/21 ] |
|
Hi sergei_grigoriev@belkatechnologies.com, Were you able to resolve your corruption? If this is still an issue for you, would you please make a complete copy of the database's $dbpath? If your topology is a replica set, we ideally perform a clean resync from an unaffected node. You can also try mongod --repair using the latest version of MongoDB. In the event that a --repair operation is unsuccessful, then please also provide: The logs leading up to the first occurrence of any issue Thanks, |
| Comment by Edwin Zhou [ 19/Jan/21 ] |
|
Hi sergei_grigoriev@belkatechnologies.com, The ideal resolution is to perform a clean resync from an unaffected node. You can also try mongod --repair using the latest version of MongoDB. In the event that a --repair operation is unsuccessful, then please also provide:
Best, |