48  * 1) on rename or unlink, if the inode being unlinked isn't in the fsync
49  * log, we must force a full commit before doing an fsync of the directory
57  * fsync foo/some_dir/some_file
59  * The fsync above will unlink the original some_dir without recording
61  * unless the fsync of some_file forces a full commit
63  * 2) we must log any new names for any file or dir that is in the fsync
79  * fsync(f1)
81  * The directory f1 was fully removed from the FS, but fsync was never
126  * Instead of doing a tree commit on every fsync, we use the
130  * and then the fsync is considered complete.
555 			 * fsync, and the inode wasn't fsynced before. In this  in overwrite_item()
1763  * for inodes that actually exist.  This means an fsync on a directory
1764  * does not implicitly fsync all the new files in it
2001 	 * xfs_io -c "fsync" testdir/bar  in replay_one_dir_item()
2036  * that means it was deleted from the directory before the fsync
2443 			 * If we have a tmpfile (O_TMPFILE) that got fsync'ed  in replay_one_buffer()
2444 			 * and never got linked before the fsync, skip it, as  in replay_one_buffer()
2475 			 * because before an fsync we can have prealloc extents  in replay_one_buffer()
2920  * fsync is to commit the whole FS.  When btrfs_sync_log returns -EAGAIN,
3462  * fsync file X
3464  * fsync dir Y
3467  * didn't get fsync'd again so the log has back refs for X and X.link.
3471  * unlinked.  Any later fsync will include the updated log entries, and
3783 		 * xfs_io -c "fsync" mydir  in process_dir_items_leaf()
3787 		 * Would result in a fsync log that when replayed, our file inode  in process_dir_items_leaf()
3824  * to replay anything deleted before the fsync
4233 	 * We do not need to set the nbytes field, in fact during a fast fsync  in fill_inode_item()
4234 	 * its value may not even be correct, since a fast fsync does not wait  in fill_inode_item()
4260 	 * If we are doing a fast fsync and the inode was logged before in the  in log_inode_item()
4276 		 * This means it is the first fsync in the current transaction,  in log_inode_item()
4279 		 * fsync and in case an inode eviction happens after the inode was  in log_inode_item()
4436 		 * few random writes into a file and then fsync it for the first  in copy_items()
4784  * lose them after doing a full/fast fsync and replaying the log. We scan the
4885 		 * get here, get rid of everything from a past fsync. After  in btrfs_log_prealloc_extents()
5252  * xfs_io -c fsync /mnt/x
5264  * xfs_io -c fsync /mnt/foo
5277  * fsync /mnt/x or fsync some new file inside it
5280  * The snapshot delete, rmdir of x, mkdir of a new x and the fsync all happen in
6469 	 *     $ xfs_io -c "fsync" a  in btrfs_log_inode()
6525 	 * directory A to a directory B, then fsync directory A, we have no way  in btrfs_log_inode()
6551 			 * 0, fsync, write 4K into offset 4096, add hard link,  in btrfs_log_inode()
6552 			 * fsync some other file (to sync log), power fail - if  in btrfs_log_inode()
6636 		 * If we are doing a fast fsync and the inode was logged before  in btrfs_log_inode()
6688 	 *    happened. We must make sure that if an explicit fsync against  in btrfs_log_inode()
6696 	 *    truncate operation, the log is synced through an fsync of  in btrfs_log_inode()
6697 	 *    some other inode and then finally an explicit fsync against  in btrfs_log_inode()
6698 	 *    this inode is made, we must make sure this fsync logs the  in btrfs_log_inode()
6704 	 *    its last_log_commit - otherwise if an explicit fsync is made  in btrfs_log_inode()
6705 	 *    against an ancestor, the fsync considers the inode in the log  in btrfs_log_inode()
6707 	 *    a power failure unless the log was synced as part of an fsync  in btrfs_log_inode()
6715 	 * Reset the last_reflink_trans so that the next fsync does not need to  in btrfs_log_inode()
6818 			 * it got fsync'ed, from existing at both parents after  in btrfs_log_all_parents()
6828 			 * fsync /mnt/B/bar  in btrfs_log_all_parents()
7136 	 * xfs_io -c fsync testdir/foo  in btrfs_log_inode_parent()
7153 	 * xfs_io -c fsync foo  in btrfs_log_inode_parent()
7389  * properly done if it is fsync'd later after the unlinks are done.
7435 	 * there we're unlinking from gets fsync'd later on, there's  in btrfs_record_unlink_dir()
7436 	 * no way to find the destination directory later and fsync it  in btrfs_record_unlink_dir()
7446  * Make sure that if someone attempts to fsync the parent directory of a deleted