https://github.com/torvalds/linux
Revision 01dea1efc23b511d3b58bb94da07ddb6d6db9895 authored by Josef Bacik on 11 November 2009, 02:23:48 UTC, committed by Chris Mason on 11 November 2009, 19:20:17 UTC
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 <josef@redhat.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
1 parent 249ac1e
History
Tip revision: 01dea1efc23b511d3b58bb94da07ddb6d6db9895 authored by Josef Bacik on 11 November 2009, 02:23:48 UTC
Btrfs: fix how we set max_size for free space clusters
Tip revision: 01dea1e
File Mode Size
Documentation
arch
block
crypto
drivers
firmware
fs
include
init
ipc
kernel
lib
mm
net
samples
scripts
security
sound
tools
usr
virt
.gitignore -rw-r--r-- 952 bytes
.mailmap -rw-r--r-- 3.9 KB
COPYING -rw-r--r-- 18.3 KB
CREDITS -rw-r--r-- 91.8 KB
Kbuild -rw-r--r-- 2.4 KB
MAINTAINERS -rw-r--r-- 148.6 KB
Makefile -rw-r--r-- 53.8 KB
README -rw-r--r-- 17.0 KB
REPORTING-BUGS -rw-r--r-- 3.3 KB

README

back to top