When different threads are inserting into databases with the same name in different cases the secondary crashes
d20001| 2016-06-14T13:25:25.593-0400 I STORAGE  [FileAllocator] allocating new datafile /data/db/testReplSet-1/dbcasetest_dbnameA.0, filling with zeroes...
d20001| 2016-06-14T13:25:25.607-0400 I STORAGE  [FileAllocator] done allocating datafile /data/db/testReplSet-1/dbcasetest_dbnameA.0, size: 16MB,  took 0.013 secs
d20001| 2016-06-14T13:25:25.641-0400 E REPL     [repl writer worker 9] Failed command { create: "bar" } on dbcasetest_dbnamea with status DatabaseDifferCase: db already exists with different case already have: [dbcasetest_dbnameA] trying to create [dbcasetest_dbnamea] during oplog application
d20001| 2016-06-14T13:25:25.641-0400 F REPL     [repl writer worker 9] Error applying operation ({ ts: Timestamp 1465925123000|7, t: 1, h: 6109000168575080191, v: 2, op: "c", ns: "dbcasetest_dbnamea.$cmd", o: { create: "bar" } }): DatabaseDifferCase: db already exists with different case already have: [dbcasetest_dbnameA] trying to create [dbcasetest_dbnamea]
d20001| 2016-06-14T13:25:25.641-0400 I -        [repl writer worker 9] Fatal assertion 16359 DatabaseDifferCase: db already exists with different case already have: [dbcasetest_dbnameA] trying to create [dbcasetest_dbnamea]
d20001| 2016-06-14T13:25:25.642-0400 I -        [repl writer worker 9] 
d20001| 
d20001| ***aborting after fassert() failure
d20001| 
- is depended on by
- 
                    SERVER-12930 More than one lock exists per logical entity(/db) -         
- Closed
 
-         
- 
                    SERVER-25411 run jstestfuzz_concurrent* on mmapv1 -         
- Closed
 
-         
- related to
- 
                    SERVER-23976 repairDatabase command on a new, different-cased database terminates server -         
- Closed
 
-