diff options
| author | Josef Bacik <[email protected]> | 2009-11-11 02:23:48 +0000 |
|---|---|---|
| committer | Chris Mason <[email protected]> | 2009-11-11 19:20:17 +0000 |
| commit | 01dea1efc23b511d3b58bb94da07ddb6d6db9895 (patch) | |
| tree | 4112505e90ab22936f4de18e15197979dd176cdc /fs/proc/array.c | |
| parent | Btrfs: cleanup transaction starting and fix journal_info usage (diff) | |
| download | kernel-01dea1efc23b511d3b58bb94da07ddb6d6db9895.tar.gz kernel-01dea1efc23b511d3b58bb94da07ddb6d6db9895.zip | |
Btrfs: fix how we set max_size for free space clusters
This patch fixes a problem where max_size can be set to 0 even though we
filled the cluster properly. We set max_size to 0 if we restart the cluster
window, but if the new start entry is big enough to be our new cluster then we
could return with a max_size set to 0, which will mean the next time we try to
allocate from this cluster it will fail. So set max_extent to the entry's
size. Tested this on my box and now we actually allocate from the cluster
after we fill it. Thanks,
Signed-off-by: Josef Bacik <[email protected]>
Signed-off-by: Chris Mason <[email protected]>
Diffstat (limited to 'fs/proc/array.c')
0 files changed, 0 insertions, 0 deletions