[SERVER-1231] --directoryperdb doesn't work with repair Created: 13/Jun/10 Updated: 28/Jun/12 Resolved: 28/Jun/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.4.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Aaron Staple |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
more details here: http://groups.google.com/group/mongodb-user/browse_thread/thread/d2dcf59b157b4526?hl=en |
| Comments |
| Comment by Aaron Staple [ 28/Jun/10 ] |
|
Haven't heard anything more, closing... |
| Comment by Aaron Staple [ 21/Jun/10 ] |
|
In my testing, directoryperdb does seem to work with repair. In the support group posting, it looks like mongod was started inconsistently - sometimes with the directoryperdb option and sometimes without. I am going to try and drill down on that discrepancy. |
| Comment by auto [ 21/Jun/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |