[SERVER-13739] Repair database failure can delete database files Created: 25/Apr/14 Updated: 11/Jul/16 Resolved: 30/Apr/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.6.0, 2.6.1-rc0 |
| Fix Version/s: | 2.6.1, 2.7.0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Chad Kreimendahl | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Backport Completed: | |
| Participants: |
| Description |
| Comments |
| Comment by Githook User [ 30/Apr/14 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by Githook User [ 30/Apr/14 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by Chad Kreimendahl [ 25/Apr/14 ] |
|
I may have forgot to add that it deleted both the temp database (cleanup seen at the end), but the failed write somehow wiped the entire directory. We do directoryPerDB, and the directory in question was deleted. It also appears that some slashes are used as cancellation characters in what I posted, so for full paths, look at the source of the original note. |