diff options
author | Liu Bo <bo.li.liu@oracle.com> | 2017-09-13 21:25:21 +0300 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2017-09-26 15:53:04 +0300 |
commit | fed3b381145e2e7c66b0b3f640851e1633ebd07f (patch) | |
tree | 97cfb34ab8188a3f67aebb344b0909f09fdb5ed3 /fs/btrfs | |
parent | c2faff790ccd11ea5be8e3ca99713f116fcd6030 (diff) | |
download | linux-fed3b381145e2e7c66b0b3f640851e1633ebd07f.tar.xz |
Btrfs: do not backup tree roots when fsync
It doesn't make sense to backup tree roots when doing fsync, since
during fsync those tree roots have not been consistent on disk.
Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
Reviewed-by: Qu Wenruo <quwenruo.btrfs@gmx.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs')
-rw-r--r-- | fs/btrfs/disk-io.c | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c index 27d458640536..0f2271815eb6 100644 --- a/fs/btrfs/disk-io.c +++ b/fs/btrfs/disk-io.c @@ -3641,7 +3641,14 @@ int write_all_supers(struct btrfs_fs_info *fs_info, int max_mirrors) u64 flags; do_barriers = !btrfs_test_opt(fs_info, NOBARRIER); - backup_super_roots(fs_info); + + /* + * max_mirrors == 0 indicates we're from commit_transaction, + * not from fsync where the tree roots in fs_info have not + * been consistent on disk. + */ + if (max_mirrors == 0) + backup_super_roots(fs_info); sb = fs_info->super_for_commit; dev_item = &sb->dev_item; |