Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.0.0-rc9, 3.1.0
Affects Version/s: 3.0.0-rc8
Component/s: Storage
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Completed:

3.0.0-rc9
Sprint:
RPL 0 3/13/15
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

A crash shortly after initializing a db directory can leave the data inaccessible due to an empty storage.bson file. An fsync of the newly written file in StorageEngineMetadata::write before allowing any db data to be written should fix this.

is related to

SERVER-15986 Starting with different storage engines in the same dbpath should error/warn

Closed

SERVER-16332 Fix coverity defect in StorageEngineMetadata::write()

Closed

SERVER-16677 mongod.lock file should be present in data directory regardless of storage engine selected

Closed

SERVER-16760 Coverity analysis defect 49690: Resource leak

Closed

related to

SERVER-17152 WiredTiger file corrupted during power cycle test

Closed

Assignee:: Benety Goh
Reporter:: Bruce Lucas (Inactive)
Participants:: Benety Goh, Bruce Lucas, Githook User
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Feb 06 2015 08:18:10 PM UTC
Updated:: Jan 25 2017 10:01:24 PM UTC
Resolved:: Feb 11 2015 07:20:34 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates