While trying to manually get statistics after a LinkBench run with logging enabled, Alex and I managed to truncate data files, then truncate the log so that data was lost. I don't have a record of the exact steps, but it involved killing MySQL without closing the connection, then running "wt stat", so we didn't expect the results we saw.

The main problems are:

• commands like "wt stat" and "wt printlog" shouldn't write files at all; and

• the "log=(enabled)" configuration is off by default, and when it is enabled, it automatically implies both running recovery and truncating logs afterwards. This makes "wt printlog" potentially remove the log files we want to examine after a crash.