summaryrefslogtreecommitdiffstats
path: root/virt/kvm
diff options
context:
space:
mode:
authorMiao Xie <miaox@cn.fujitsu.com>2012-09-07 01:43:32 -0600
committerChris Mason <chris.mason@fusionio.com>2012-10-01 15:19:17 -0400
commit8407aa464331556e4f6784f974030b83fc7585ed (patch)
treea522976de80295edd552d08fd5ff897e05e07d1e /virt/kvm
parent837e197283199de640857192ca32767cb6e24fe8 (diff)
downloadop-kernel-dev-8407aa464331556e4f6784f974030b83fc7585ed.zip
op-kernel-dev-8407aa464331556e4f6784f974030b83fc7585ed.tar.gz
Btrfs: fix corrupted metadata in the snapshot
When we delete a inode, we will remove all the delayed items including delayed inode update, and then truncate all the relative metadata. If there is lots of metadata, we will end the current transaction, and start a new transaction to truncate the left metadata. In this way, we will leave a inode item that its link counter is > 0, and also may leave some directory index items in fs/file tree after the current transaction ends. In other words, the metadata in this fs/file tree is inconsistent. If we create a snapshot for this tree now, we will find a inode with corrupted metadata in the new snapshot, and we won't continue to drop the left metadata, because its link counter is not 0. We fix this problem by updating the inode item before the current transaction ends. Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud