From: Liu Bo Date: Thu, 1 Nov 2012 06:38:47 +0000 (+0000) Subject: Btrfs: do not log extents when we only log new names X-Git-Tag: accepted/tizen/common/20141203.182822~2921^2~104 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=183f37fa3503332740c76f1b493f4304ec889358;p=platform%2Fkernel%2Flinux-arm64.git Btrfs: do not log extents when we only log new names When we log new names, we need to log just enough to recreate the inode during log replay, and there is no need to log extents along with it. This actually fixes a bug revealed by xfstests 241, where it shows that we're logging some extents that have not updated metadata, so we don't get proper EXTENT_DATA items to be copied to log tree. Signed-off-by: Liu Bo Signed-off-by: Chris Mason --- diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c index 81e407d..4ec41ec 100644 --- a/fs/btrfs/tree-log.c +++ b/fs/btrfs/tree-log.c @@ -3435,7 +3435,8 @@ static int btrfs_log_inode(struct btrfs_trans_handle *trans, ret = btrfs_truncate_inode_items(trans, log, inode, 0, 0); } else { - fast_search = true; + if (inode_only == LOG_INODE_ALL) + fast_search = true; max_key.type = BTRFS_XATTR_ITEM_KEY; ret = drop_objectid_items(trans, log, path, ino, BTRFS_XATTR_ITEM_KEY);