aboutsummaryrefslogtreecommitdiffstats
path: root/fs/btrfs
diff options
context:
space:
mode:
authorJosef Bacik <josef@redhat.com>2010-10-26 12:55:03 -0400
committerJosef Bacik <josef@redhat.com>2010-10-26 12:55:03 -0400
commite9bb7f10d3617304ef94ff7aa8fefbce3078f08b (patch)
tree0e56ad5bd8b4914aa82103d72531f8c95b35ce80 /fs/btrfs
parent382279336f428c80f344edfc30d53797e3e76146 (diff)
Btrfs: remove warn_on from use_block_rsv
Because btrfs_dirty_inode does a btrfs_join_transaction, it doesn't actually reserve space. It does this so we can try and dirty the inode quickly without having to deal with the ENOSPC problems. But if it does get back ENOSPC it handles it properly. The problem is use_block_rsv does a WARN_ON whenever this case happens, even tho btrfs_dirty_inode takes it into account and actually expects to get -ENOSPC if things are particularly tight. So instead just remove the warning. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com>
Diffstat (limited to 'fs/btrfs')
-rw-r--r--fs/btrfs/extent-tree.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index e2dfd4ab3b9b..33785333f293 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -5358,11 +5358,6 @@ use_block_rsv(struct btrfs_trans_handle *trans,
5358 if (!ret) 5358 if (!ret)
5359 return block_rsv; 5359 return block_rsv;
5360 5360
5361 WARN_ON(1);
5362 printk(KERN_INFO"block_rsv size %llu reserved %llu freed %llu %llu\n",
5363 block_rsv->size, block_rsv->reserved,
5364 block_rsv->freed[0], block_rsv->freed[1]);
5365
5366 return ERR_PTR(-ENOSPC); 5361 return ERR_PTR(-ENOSPC);
5367} 5362}
5368 5363