[SERVER-17571] WiredTiger unable to start if crash leaves 0-length WiredTiger file Created: 12/Mar/15 Updated: 19/Jun/15 Resolved: 19/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | 3.0.2, 3.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Susan LoVerso |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
A crash can leave the WiredTiger.basecfg file existing but empty, and in that case WiredTiger won't start. The file should be fsync'ed after being created. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 19/Apr/15 ] |
|
The fix in WT was already merged in for 3.0.2 |