Hi All, Commit 22de5d7741f963e57dd5e3bb70d822e992dd2515 seems to have changed how Windows works with the default invalidate parameter. Previously it was not needed to specify invalidate=0, but now it is needed on Windows. Without it, fio reports: fio-2.21 Starting 1 thread fio: cache invalidation of \\.\PHYSICALDRIVE1 failed: Unknown error fio: cache invalidation of \\.\PHYSICALDRIVE1 failed: Unknown error Is the expectation that Windows default invalidate (1) should silently ignore this issue, or must the user specify invalidate=0 on Windows platforms? Thanks. Regards, Jeff -- 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
