[Resending without HTML] 2012/9/18 Nicholas A. Bellinger <nab@xxxxxxxxxxxxxxx>: > Also note that by default it's my understanding that IETD uses buffered > FILEIO for performance, so in your particular type of setup you'd still > see better performance with buffered FILEIO, but would still have the > potential risk of silent data corruption with buffered FILEIO. Nicholas, IETs fileio defaults to writethrough caching (by issueing a sync after writing and before returning a response to the client). Writeback behaviour as employed by the OP needs to be switched on explicitly. Also, the failure scenario for writeback caching you're referring to is neither silent data corruption (as pointed out by Peter already) nor silent data loss, as the WCE bit makes it pretty clear to the client side that data is not guaranteed to be on persistent storage unless explicitly flushed. Arne -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
