path: root/fs/btrfs/free-space-cache.c
diff options
authorJosef Bacik <josef@redhat.com>2011-10-18 13:07:31 -0400
committerJosef Bacik <josef@redhat.com>2011-10-19 15:13:00 -0400
commit7e355b83efa80e5f5821591c13c17649594d82ac (patch)
tree978b21df0e2a77a16fe8383be28a82378a7d662d /fs/btrfs/free-space-cache.c
parent36ba022ac0b748dd543f43430b03198e899426c9 (diff)
Btrfs: if we have a lot of pinned space, commit the transaction
Mitch kept hitting a panic because he was getting ENOSPC. One of my previous patches makes it so we are much better at not allocating new metadata chunks. Unfortunately coupled with the overcommit patch this works us into a bit of a problem if we are removing a bunch of space and end up chewing up all of our space with pinned extents. We can allocate chunks fine and overflow is ok, but the only way to reclaim this space is to commit the transaction. So if we go to overcommit, first check and see how much pinned space we have. If we have more than 80% of the free space chewed up with pinned extents, just commit the transaction, this will free up enough space for our reservation and we won't have this problem anymore. With this patch Mitch's test doesn't blow up anymore. Thanks, Reported-and-tested-by: Mitch Harder <mitch.harder@sabayonlinux.org> Signed-off-by: Josef Bacik <josef@redhat.com>
Diffstat (limited to 'fs/btrfs/free-space-cache.c')
0 files changed, 0 insertions, 0 deletions