|author||Josef Bacik <email@example.com>||2012-08-06 13:46:38 -0600|
|committer||Chris Mason <firstname.lastname@example.org>||2012-08-28 16:53:34 -0400|
Btrfs: increase the size of the free space cache
Arne was complaining about the space cache having mismatching generation numbers when debugging a deadlock. This is because we can run out of space in our preallocated range for our space cache if you have a pretty fragmented amount of space in your pinned space. So just increase the amount of space we preallocate for space cache so we can be sure to have enough space. This will only really affect data ranges since their the only chunks that end up larger than 256MB. Thanks, Signed-off-by: Josef Bacik <email@example.com> Signed-off-by: Chris Mason <firstname.lastname@example.org>
1 files changed, 7 insertions, 8 deletions
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index d3df65f83b5..1bb408f737f 100644
@@ -2975,17 +2975,16 @@ again:
- num_pages = (int)div64_u64(block_group->key.offset, 1024 * 1024 * 1024);
+ * Try to preallocate enough space based on how big the block group is.
+ * Keep in mind this has to include any pinned space which could end up
+ * taking up quite a bit since it's not folded into the other space
+ * cache.
+ num_pages = (int)div64_u64(block_group->key.offset, 256 * 1024 * 1024);
num_pages = 1;
- * Just to make absolutely sure we have enough space, we're going to
- * preallocate 12 pages worth of space for each block group. In
- * practice we ought to use at most 8, but we need extra space so we can
- * add our header and have a terminator between the extents and the
- * bitmaps.
num_pages *= 16;
num_pages *= PAGE_CACHE_SIZE;