Ouch, you're right, I didn't think of that problem.

I don't like silently disabling direct I/O on files, that would mess up benchmarks, I'd rather see a specific error message.

We could "correct" if the file is being created, otherwise it's an error?

Anyway, you're correct and I'm willing to go in either direction, but prefer failure rather than silently turning off direct I/O.