[SERVER-2711] Starting mongod on dbpath with journal shouldn't advise repair Created: 08/Mar/11 Updated: 12/Jul/16 Resolved: 18/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Suppose you're running with --dur, that you then have an unclean shutdown. If you manage to start a mongod and forget --dur, the mongod exits with the old message about removing the lock file and running repair. Ideally we shouldn't tell people to run repair if they've got a journal, but should instead tell them to run with --dur, as we do if they start up without --dur and the journal exists but the lock file doesn't. |
| Comments |
| Comment by Mathias Stearn [ 15/Aug/11 ] |
|
Not sure why this wasn't closed... |
| Comment by Tony Hannan [ 15/Aug/11 ] |
|
Since --journal is default we need to update error message below when starting with --nojournal: ************** |
| Comment by auto [ 18/Mar/11 ] |
|
Author: {u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'redbeard0531@gmail.com'}Message: remove non-recomended alternative |
| Comment by auto [ 18/Mar/11 ] |
|
Author: {u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'redbeard0531@gmail.com'}Message: don't repeat error message |
| Comment by auto [ 18/Mar/11 ] |
|
Author: {u'login': u'dwight', u'name': u'dwight', u'email': u'dwight@10gen.com'}Message: bad error msg |