afaics a write behind strategy means you will report a write as being complete before it has actually been written. This can result in terrific performance beca

afaics a write behind strategy means you will report a write as being complete before it has actually been written. This can result in terrific performance because your batching window is larger and you can amortize more (fewer?) iops. But it also means in the face of failure, clients could believe something was written which wasn't. On the other hand, the storage device can fail so what does it even mean to have written the data? :)