On Thu, Dec 02, 2010 at 04:16:59PM -0800, Darrick J. Wong wrote: > If the user tries to enable write flushes with "barrier=1" and the underlying > block device does not support flushes, print a message and set barrier=0. That doesn't make any sense at all with the ne wFLUSH+FUA code, which is designed to make the cache flushing entirely transparanent. Basically with the new code the barrier option should become a no-op and always enabled. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
