Btrfs: check unused against how much space we actually want
authorJosef Bacik <josef@redhat.com>
Thu, 22 Sep 2011 18:30:02 +0000 (14:30 -0400)
committerJosef Bacik <josef@redhat.com>
Wed, 19 Oct 2011 19:12:47 +0000 (15:12 -0400)
There is a bug that may lead to early ENOSPC in our reservation code.  We've
been checking against num_bytes which may be above and beyond what we want to
actually reserve, which could give us a false ENOSPC.  Fix this by making sure
the unused space is above how much we want to reserve and not how much we're
trying to flush.  Thanks,

Signed-off-by: Josef Bacik <josef@redhat.com>
fs/btrfs/extent-tree.c

index 5498bdacd4c301eeb0d39f145adbccb568550152..fd65f6bc676c9c5e0d2b0c900e7f95fc9b5c63e4 100644 (file)
@@ -3472,7 +3472,7 @@ again:
         */
        if (unused <= space_info->total_bytes) {
                unused = space_info->total_bytes - unused;
-               if (unused >= num_bytes) {
+               if (unused >= orig_bytes) {
                        space_info->bytes_may_use += orig_bytes;
                        ret = 0;
                } else {