summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/extent-tree.c
diff options
context:
space:
mode:
authorJosef Bacik <josef@redhat.com>2010-10-26 18:55:03 +0200
committerJosef Bacik <josef@redhat.com>2010-10-26 18:55:03 +0200
commite9bb7f10d3617304ef94ff7aa8fefbce3078f08b (patch)
tree0e56ad5bd8b4914aa82103d72531f8c95b35ce80 /fs/btrfs/extent-tree.c
parentBtrfs: set trans to null in reserve_metadata_bytes if we commit the transaction (diff)
downloadlinux-e9bb7f10d3617304ef94ff7aa8fefbce3078f08b.tar.xz
linux-e9bb7f10d3617304ef94ff7aa8fefbce3078f08b.zip
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 '')
-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,
if (!ret)
return block_rsv;
- WARN_ON(1);
- printk(KERN_INFO"block_rsv size %llu reserved %llu freed %llu %llu\n",
- block_rsv->size, block_rsv->reserved,
- block_rsv->freed[0], block_rsv->freed[1]);
-
return ERR_PTR(-ENOSPC);
}