When the journal files are wiped/truncated, like during fsync+lock, a marker file should be written so if a backup is made, or the server crashes, the server can automatically restart instead of complaining about a lock file but no journal files.
There are many cases where this happens, like dropDatabase, moveChunk, and repair.
This may be MMapV1 specific.
- is duplicated by
-
SERVER-19778 Mongod recovery fails after power cycle, mmap storage, no journal files present
- Closed
- is related to
-
SERVER-8358 "Move chunk commit failed" shutdown leaves mongod with no journal files and mongod.lock file
- Closed
-
SERVER-19707 A crash after dropDatabase leaves the server unable to restart
- Closed