Test1 the restart when can't Write data in Disk

Step1. Write the hook.so for Write and Export to the system
Step2. Restart the MongoDB
Result: Mongo DB will terminating, and check the src code when MongoDB write PID file failure ,below is the failure code fragment and log of MongoD. attachment you can check

So the question is what's the exception code return when insert data into Disk failure and application call ,and in the runTime model,insert data failure ,what's result on MongoD

Test2

After started mongod and inserting a document to allocate the space, I filled the volume with "cat /dev/zero > /Volume/test/bigfile".
I inserted another document and then it crashed.

Here is the stack trace:

Mon Sep 3 17:34:42 [journal] LogFile::synchronousAppend failed with 8192 bytes unwritten out of 8192 bytes; b=0x111000000 errno:28 No space left on device
Mon Sep 3 17:34:42 [journal] Fatal Assertion 13515
0x10037637b 0x1000aeeb5 0x1002319c6 0x100107471 0x1001076e2 0x10023eddb 0x100240090 0x1002426ed 0x1005a7823 0x7fff8e3568bf 0x7fff8e359b75
0 mongod 0x000000010037637b _ZN5mongo15printStackTraceERSo + 43
1 mongod 0x00000001000aeeb5 _ZN5mongo13fassertFailedEi + 165
2 mongod 0x00000001002319c6 _ZN5mongo7LogFile17synchronousAppendEPKvm + 326
3 mongod 0x0000000100107471 _ZN5mongo3dur7Journal7journalERKNS0_11JSectHeaderERKNS_14AlignedBuilderE + 769
4 mongod 0x00000001001076e2 _ZN5mongo3dur14WRITETOJOURNALENS0_11JSectHeaderERNS_14AlignedBuilderE + 50
5 mongod 0x000000010023eddb _ZN5mongo3dur27groupCommitWithLimitedLocksEv + 411
6 mongod 0x0000000100240090 _ZN5mongo3durL20durThreadGroupCommitEv + 208
7 mongod 0x00000001002426ed _ZN5mongo3dur9durThreadEv + 1117
8 mongod 0x00000001005a7823 thread_proxy + 163
9 libsystem_c.dylib 0x00007fff8e3568bf _pthread_start + 335
10 libsystem_c.dylib 0x00007fff8e359b75 thread_start + 13
Mon Sep 3 17:34:42 [journal]

***aborting after fassert() failure

Mon Sep 3 17:34:42 Got signal: 6 (Abort trap: 6).

Mon Sep 3 17:34:42 Backtrace:
0x10037637b 0x100001a6b 0x7fff8e3aacfa 0x17fffffff 0x7fff8e349a7a 0x1000aeef0 0x1002319c6 0x100107471 0x1001076e2 0x10023eddb 0x100240090 0x1002426ed 0x1005a7823 0x7fff8e3568bf 0x7fff8e359b75
0 mongod 0x000000010037637b _ZN5mongo15printStackTraceERSo + 43
1 mongod 0x0000000100001a6b _ZN5mongo10abruptQuitEi + 987
2 libsystem_c.dylib 0x00007fff8e3aacfa _sigtramp + 26
3 ??? 0x000000017fffffff 0x0 + 6442450943
4 libsystem_c.dylib 0x00007fff8e349a7a abort + 143
5 mongod 0x00000001000aeef0 _ZN5mongo13fassertFailedEi + 224
6 mongod 0x00000001002319c6 _ZN5mongo7LogFile17synchronousAppendEPKvm + 326
7 mongod 0x0000000100107471 _ZN5mongo3dur7Journal7journalERKNS0_11JSectHeaderERKNS_14AlignedBuilderE + 769
8 mongod 0x00000001001076e2 _ZN5mongo3dur14WRITETOJOURNALENS0_11JSectHeaderERNS_14AlignedBuilderE + 50
9 mongod 0x000000010023eddb _ZN5mongo3dur27groupCommitWithLimitedLocksEv + 411
10 mongod 0x0000000100240090 _ZN5mongo3durL20durThreadGroupCommitEv + 208
11 mongod 0x00000001002426ed _ZN5mongo3dur9durThreadEv + 1117
12 mongod 0x00000001005a7823 thread_proxy + 163
13 libsystem_c.dylib 0x00007fff8e3568bf _pthread_start + 335
14 libsystem_c.dylib 0x00007fff8e359b75 thread_start + 13

db.getLastError(WriteConcern.FSYNC_SAFE)