[SERVER-12989] journal file cleanup failure post mongod termination with ctrl-c on windows 8 Created: 02/Mar/14 Updated: 10/Dec/14 Resolved: 10/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shailesh Tak | Assignee: | Mark Benvenuto |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | run mongod |
| Participants: |
| Description |
|
looks like journal and lock files are not getting cleaned post ctrl-c on mongod in windows. c:\Programs\MongoDB\2.6.0-rc0\bin>mongod --dbpath C:\Programs\MongoDB\2.6.0-rc0\data --port 27017 --cpu --quiet , storage: { dbPath: "C:\Programs\MongoDB\2.6.0-rc0\data" }, sy } |
| Comments |
| Comment by Ramon Fernandez Marina [ 10/Jun/14 ] |
|
Hi shaileshtak, we haven't heard back from you for some time, so I'm going to mark this issue as resolved. If this is still an issue for you, please feel free to re-open the ticket and answer Mark's question above (dir /s ...) to help us reproduce the problem. Regards, |
| Comment by Thomas Rueckstiess [ 16/Apr/14 ] |
|
Hi Shailesh, Just checking in to see if you can run the additional "dir" after the repro fails, as that would help us with the diagnosis of the issue. If you can share any additional information that might potentially be helpful to reproduce, that would be great also. Thanks, |
| Comment by Mark Benvenuto [ 04/Mar/14 ] |
|
I tried on a different machine today (first machine was SSD based, and not virtual, new machine was EC2 based virtual machine) to try to repro the problem. I still cannot repro it. When it fails, can you run to see what files remain after it fails, and post this to the bug. |
| Comment by Shailesh Tak [ 04/Mar/14 ] |
|
Mark, My Windows version details. I will keep trying to see if I can give you repeatable test case, as it Here is the output from windows I initiated mongod. , storage: { dbPath: "C:\Programs\MongoDB\2.6.0-rc0\data" } } – Regards 'Peace and Joy on the Universe' |
| Comment by Mark Benvenuto [ 03/Mar/14 ] |
|
I cannot reproduce this bug. I wrote a script to start mongod, and hit control-C on mongod after a random sleep 60 times without hitting an assert. What file was left behind? Also, it appears you are running on Windows 7 according to this version number instead of Windows 8. 2014-03-02T15:17:51.987-0500 [initandlisten] build info: windows sys.getwindowsversion(major=6, minor=1, build=7601, platform=2, service_pack='Service |