On 4/3/2014 9:28 PM, Jens Axboe wrote:
This really sounds like an issue with write() on windows. The change looks fine, and the fact that moving the memset around makes a difference - well, that's just bizarre. Do you have time to dig into this? Was read/write really completely reliable before this change?
It turns out it was a problem with open() - you need to pass _O_BINARY to avoid Windows trying to interpret file contents.
-- Bruce -- 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
