Btrfs: fix missing log when BTRFS_INODE_NEEDS_FULL_SYNC is set
If we set BTRFS_INODE_NEEDS_FULL_SYNC, we should log all the extent, but now we forget to take it into account, and set a wrong max key, if so, we will skip the file extent metadata when doing logging. Fix it. Signed-off-by: Miao Xie <miaox@cn.fujitsu.com> Signed-off-by: Chris Mason <chris.mason@fusionio.com>
This commit is contained in:
parent
bbe1426764
commit
5269b67e3d
|
@ -3394,7 +3394,10 @@ static int btrfs_log_inode(struct btrfs_trans_handle *trans,
|
||||||
|
|
||||||
|
|
||||||
/* today the code can only do partial logging of directories */
|
/* today the code can only do partial logging of directories */
|
||||||
if (inode_only == LOG_INODE_EXISTS || S_ISDIR(inode->i_mode))
|
if (S_ISDIR(inode->i_mode) ||
|
||||||
|
(!test_bit(BTRFS_INODE_NEEDS_FULL_SYNC,
|
||||||
|
&BTRFS_I(inode)->runtime_flags) &&
|
||||||
|
inode_only == LOG_INODE_EXISTS))
|
||||||
max_key.type = BTRFS_XATTR_ITEM_KEY;
|
max_key.type = BTRFS_XATTR_ITEM_KEY;
|
||||||
else
|
else
|
||||||
max_key.type = (u8)-1;
|
max_key.type = (u8)-1;
|
||||||
|
|
Loading…
Reference in New Issue