Does anyone have an explanation why nfs calls write_inode_now before doing a sillrename? The comment above claims that we want to start an asynchronous writeout, but given that NFS doesn't have dirty inode metadata that needs to be written back from ->write_inode this only starts data writeback. And that should be done using filemap_fdatawrite or filemap_flush. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html