Some replsets tests check that a

write on a server with --nojournal fails. The method to detect whether an engine is journaling is `StorageEngine::isDurable()'

Some engines are unconditionally durable, so they always return true for isDurable and ignore the --nojournal option. As a result the write command API won't reject writes due to

because it seems like a valid thing to do (and it is because the engine supports journaling).

If we want to keep the current semantics, we should check for the '--nojournal' option in the command line params struct instead of asking the storage engine whether or not it is durable. But I think the tests should just be fixed to accept the fact that some engines always enable journaling.

The tests that fail include:
jstests/gle/gle_sharded_wc.js
jstests/replsets/bulk_api_wc.js
jstests/replsets/batch_write_command_wc.js