summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/free-space-cache.c
diff options
context:
space:
mode:
authorJosef Bacik <josef@redhat.com>2011-08-29 17:01:31 +0200
committerJosef Bacik <josef@redhat.com>2011-10-19 21:12:40 +0200
commit4a33854257764c2ec6337ee0c8ecafb64f8e29e1 (patch)
tree2070f0d4a53c9124d2ff44c78e13f45ae184298c /fs/btrfs/free-space-cache.c
parentBtrfs: don't increase the block_rsv's size when emergency allocating space (diff)
downloadlinux-4a33854257764c2ec6337ee0c8ecafb64f8e29e1.tar.xz
linux-4a33854257764c2ec6337ee0c8ecafb64f8e29e1.zip
Btrfs: set truncate block rsv's size
While debugging a different issue I noticed that we were always reserving space when we tried to use our truncate block rsv's. This is because they didn't have a ->size value, so use_block_rsv just assumes there is nothing reserved and it does a reserve_metadata_bytes. This is because btrfs_check_block_rsv() doesn't actually add to the size of the block rsv. That seems to be the right thing to do so set ->size to the minimum truncate size we need, since we will always only refill to that size anyway, and this way everything works out correctly. Signed-off-by: Josef Bacik <josef@redhat.com>
Diffstat (limited to 'fs/btrfs/free-space-cache.c')
0 files changed, 0 insertions, 0 deletions