On Thu, Aug 06, 2015 at 06:00:42AM -0700, Sage Weil wrote: > I'm guessing the strategy here should be to fsync the file (leaf) and then > any affected ancestors, such that the directory fsyncs are effectively > no-ops? Or does it matter? All metadata transactions log the involve parties (parent and child inode(s) mostly) in the same transaction. So flushing one of them out is enough. But file data I/O might dirty the inode before flushing them out, so to not need to write out the inode log item twice you first want to fsync any file that had data I/O followed by directories or special files that only had metadata modified. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
