When we create namespace files under MMAPv1 we create and initialize to 0 the contents in 1MB increments. If mongoD receives a SIGKILL during this process, it is possible for a file to be written that does not fall on a 1MB boundary which is larger than the guaranteed atomic write size (at least by default, both on Linux and Windows with our current implementation).
When mongoD is restarted with the invalid namespace file in place, it will fatally assert when it finds that this file is not a multiple of 1MB.
- is duplicated by
-
SERVER-21475 Powercycle: mongod cannot recover if server host crashes during a drop database, for mmapv1
-
- Closed
-
- related to
-
SERVER-27156 disable no-journal hard kill in repl7.js
-
- Closed
-
-
-
- Closed
-