If no error is generated then it is easy to accidentally change the storage option and think your data has disappeared, or have extra and unused files.
This can be done by storing a metadata file about what storage engine was used to create the persistent storage so that we can detect if an attempt is used to use a different storage engine after that.
- is depended on by
-
SERVER-16332 Fix coverity defect in StorageEngineMetadata::write()
- Closed
-
SERVER-16567 extend data directory metadata to hold storage engine creation settings for startup validation
- Closed
- is duplicated by
-
SERVER-16175 allowing multiple storage engines in same dbpath creates opportunity for error
- Closed
-
SERVER-16116 Server should not start if datafiles from other storage engine are present in dbpath
- Closed
- related to
-
SERVER-16283 Can't start new wiredtiger node with log file or config file in data directory - false detection of old mmapv1 files
- Closed
-
SERVER-17210 Crash can leave data inaccessible due to empty storage.bson file
- Closed