[SERVER-28876] fsyncLock results in corrupt disk snapshot Created: 20/Apr/17 Updated: 31/May/17 Resolved: 01/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dharshan Rangegowda | Assignee: | Mark Agarunov |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
I am using server 3.2.12. FsyncLock() commands appear to corrupt the disk data such that a snapshot taken at this time does not work. Once the mongod process starts again on the snapshot disk it appears to ignore all the existing data files - none of the previous databases are shown. I am able to reproduce the issue consistently. Here are my steps I have attached a .zip of mongodb data folder from my tests. Here is the login credential for initial data 1. initialdata.zip - initial data |
| Comments |
| Comment by Mark Agarunov [ 01/May/17 ] |
|
Hello dharshanr@scalegrid.net, Thank you for the report. Looking over the output you've provided, this behavior appears to have the same cause as Thanks, |
| Comment by Dharshan Rangegowda [ 20/Apr/17 ] |
|
Also I have tried the same steps on 3.2.3 and it works fine. |