core/fsync.js has been (relatively) recently rewritten, and as such is superior to noPassthroughWithMongod/fsync2.js in most ways. It also gets coverage in the parallel tester. Rather than improve fsync2.js or move it to the parallel testing suite, we should simply remove it and improve fsync.js to take on any coverage lost in fsync2.js.

Original Description

Currently fsync2.js is excluded from parallel testing due to an earlier bug where fsyncLock would block reads. With the resolution of SERVER-4243, fsync2.js can now be run in parallel with most jstests.

The only tests that should not run in parallel with those that perform fsyncLock are tests that enable profiling and test system.profile content.

fsync2.js should join the profiling tests in the parallelTester list, which runs all tests in the list serially, preventing overlap.