Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.6.6, 2.8.0-rc2
Affects Version/s: 2.8.0-rc0
Component/s: Storage, Usability
Labels:
None

Operating System:
ALL
Backport Completed:

2.6.6
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

(1 related to)

Assignee:: Benety Goh
Reporter:: Scott Hernandez (Inactive)
Participants:: Benety Goh, Githook User, Scott Hernandez
Votes:: 2 Vote for this issue
Watchers:: 14 Start watching this issue

Created:: Nov 06 2014 12:41:50 PM UTC
Updated:: Oct 27 2015 02:12:18 PM UTC
Resolved:: Nov 24 2014 09:42:02 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates