From our limited testing, it would appear that Apple's new filesystem APFS does not conform to our expectations for fsync behavior. Running tests resulted in an error of the form:
[MongoDFixture:job0] 2017-11-06T10:04:51.304-0500 E STORAGE [conn331] WiredTiger error (0) [1509980691:304818][20778:0x700001ffc000], file:collection-2448-3901112796450791690.wt, WT_CURSOR.next: read checksum error for 4096B block at offset 6332416: block header checksum of 0 doesn't match expected checksum of 1222340184 [MongoDFixture:job0] 2017-11-06T10:04:51.304-0500 E STORAGE [conn331] WiredTiger error (0) [1509980691:304927][20778:0x700001ffc000], file:collection-2448-3901112796450791690.wt, WT_CURSOR.next: collection-2448-3901112796450791690.wt: encountered an illegal file format or internal value: (__wt_block_read_off, 227) [MongoDFixture:job0] 2017-11-06T10:04:51.304-0500 E STORAGE [conn331] WiredTiger error (-31804) [1509980691:304943][20778:0x700001ffc000], file:collection-2448-3901112796450791690.wt, WT_CURSOR.next: the process must exit and restart: WT_PANIC: WiredTiger library panic [MongoDFixture:job0] 2017-11-06T10:04:51.304-0500 F - [conn331] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 361 [MongoDFixture:job0] 2017-11-06T10:04:51.304-0500 F - [conn335] Fatal Assertion 28559 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 64 [MongoDFixture:job0] 2017-11-06T10:04:51.305-0500 F - [conn331] [MongoDFixture:job0] [MongoDFixture:job0] ***aborting after fassert() failure
This ticket is to track the diagnosis of this, and to come up with a better reproducer.
- is depended on by
-
SERVER-33002 Platform Support: add MacOS 10.13 (High Sierra)
- Closed
- related to
-
WT-4018 Checkpoint integrity test indicates MacOS 10.13 fsync bug
- Closed
-
SERVER-31647 Benchmark performance against APFS
- Closed
- links to