crash_test to run with data sync on

Summary: Mode of data sync off is a much less used than the case of data sync on. Crash test should cover the more common case than a corner case. So turn data sync on in crash tests.

Test Plan: Run crash test and make sure it can run with expected parameters pased to db_stres.

Reviewers: IslamAbdelRahman, anthony, igor, rven, kradhakrishnan, yhchiang

Reviewed By: yhchiang

Subscribers: leveldb, dhruba

Differential Revision: https://reviews.facebook.net/D48729

tools/db_crashtest.py

@@ -103,7 +103,7 @@ def main(argv):
                 --sync=0
                 --progress_reports=0
                 --disable_wal=0
-                --disable_data_sync=1
+                --disable_data_sync=0
                 --target_file_size_base=16777216
                 --target_file_size_multiplier=1
                 --max_write_buffer_number=3
@@ -143,7 +143,7 @@ def main(argv):
                 --sync=0
                 --progress_reports=0
                 --disable_wal=0
-                --disable_data_sync=1
+                --disable_data_sync=0
                 --target_file_size_base=2097152
                 --target_file_size_multiplier=2
                 --max_write_buffer_number=3

tools/db_crashtest2.py

@@ -124,7 +124,7 @@ def main(argv):
                 --sync=0
                 --progress_reports=0
                 --disable_wal=0
-                --disable_data_sync=1
+                --disable_data_sync=0
                 --target_file_size_base=16777216
                 --target_file_size_multiplier=1
                 --max_write_buffer_number=3
@@ -163,7 +163,7 @@ def main(argv):
                 --sync=0
                 --progress_reports=0
                 --disable_wal=0
-                --disable_data_sync=1
+                --disable_data_sync=0
                 --target_file_size_base=2097152
                 --target_file_size_multiplier=2
                 --max_write_buffer_number=3