[SERVER-41420] repair after crash due to a full storage Created: 31/May/19 Updated: 11/Jun/19 Resolved: 05/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Build |
| Affects Version/s: | 4.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | thomas poidevin | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | SWNA, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | mongod --dbpath /var/lib/mongodb --repair |
| Participants: |
| Description |
|
Hi, I m on unbutu 16 and i tryied to do that : mongod --dbpath /var/lib/mongodb --repair
I tryied to do that more than once , but still the same issue. Even when i add --nojournal it doesn't work Thanks a lot
|
| Comments |
| Comment by Eric Sedor [ 11/Jun/19 ] |
|
tigrou34; I did want to add one more thing: We don't support the method described in the blog you linked. Our recommended course of action for this error in the future would be to first attempt an initial sync from an unaffected replica set node, and then try --repair using MongoDB version 4.0.9. |
| Comment by Eric Sedor [ 05/Jun/19 ] |
|
tigrou34 We are glad to hear this! Thank you for letting us know. |
| Comment by thomas poidevin [ 05/Jun/19 ] |
|
I foudn the solution !! So i did:
I hope it help someone else
|
| Comment by thomas poidevin [ 04/Jun/19 ] |
|
Here is the log of mongod after the failed repair log_after_repair_failed.log |
| Comment by thomas poidevin [ 04/Jun/19 ] |
|
Thanks Eric Disk is a ssd disk of 50go with no raid system (we have upgraded since but nothing change, still the same issue). I didn't upgrade anything on this server since the beginning of this project (hardware and mongo). I join log when the crash came and you see the error after the reboot (crash_mongo_first_error.log) . Also you can see the error when i m using this command : mongod --repair --dbpath /var/lib/mongodb/ in the log "log_repair.log" When i restart mongo without --repair , i have the same error than before the repair. For information , i tried to create a new cloud server and run mongodb but still the same error, so it s not a disk error isn't it? Thansk a lot for your help |
| Comment by Eric Sedor [ 03/Jun/19 ] |
|
tigrou34, this error message leads us to suspect some form of physical corruption. Please make a complete copy of the database's $dbpath directory to work off of and safeguard the current $dbpath. Our ability to determine the source of this corruption depends greatly on your ability to provide:
The ideal resolution is to perform a clean resync from an unaffected node. Can you please also provide specific detail around what you mean when you say "systematically, after a while" Thanks in advance. |