diff options
| author | Miao Xie <miaox@cn.fujitsu.com> | 2014-09-03 17:35:34 +0400 |
|---|---|---|
| committer | Chris Mason <clm@fb.com> | 2014-09-18 00:38:34 +0400 |
| commit | ce7213c70c37e3a66bc0b50c45edcbfea505f62f (patch) | |
| tree | 3b458f3f28ae3d69f508b4bd9194a264f74f6f34 /fs/btrfs/transaction.c | |
| parent | 935e5cc935bcbf9b3d0dd59fed7dbc0f2ebca6bc (diff) | |
| download | linux-ce7213c70c37e3a66bc0b50c45edcbfea505f62f.tar.xz | |
Btrfs: fix wrong device bytes_used in the super block
device->bytes_used will be changed when allocating a new chunk, and
disk_total_size will be changed if resizing is successful.
Meanwhile, the on-disk super blocks of the previous transaction
might not be updated. Considering the consistency of the metadata
in the previous transaction, We should use the size in the previous
transaction to check if the super block is beyond the boundary
of the device.
Though it is not big problem because we don't use it now, but anyway
it is better that we make it be consistent with the common metadata,
maybe we will use it in the future.
Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'fs/btrfs/transaction.c')
| -rw-r--r-- | fs/btrfs/transaction.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c index 2f7c0bef4043..16d0c1b62b3e 100644 --- a/fs/btrfs/transaction.c +++ b/fs/btrfs/transaction.c @@ -1869,6 +1869,7 @@ int btrfs_commit_transaction(struct btrfs_trans_handle *trans, sizeof(*root->fs_info->super_copy)); btrfs_update_commit_device_size(root->fs_info); + btrfs_update_commit_device_bytes_used(root, cur_trans); spin_lock(&root->fs_info->trans_lock); cur_trans->state = TRANS_STATE_UNBLOCKED; |