On 2011-10-25 22:33, Steven Lang wrote: > The verify_dump option is defined and documented, but does nothing. > This one-liner enables the option. > > One thing I wanted to open a small discussion on is the default > behavior. When the verify dump behavior was added, it was something > new, so it seems more sensible to disable it by default to keep the > old behavior; and had it been in for less time I might have been > tempted to include that in the patch. However, even ignoring the > change in behavior, it seems odd and possibly surprising/unexpected to > someone who does not have experience with fio to have it suddenly spit > out extra files; all the other options to write files > (write_iolog/write_bw_log/write_lat_log) only write anything if > requested. Is there a good argument to why this option would be > enabled by default? Thanks, applied. You are right, it probably should have been off by default, and in fact probably should be even now. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
