From: Josef Bacik <josef@redhat.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: make sure to update total_bitmaps when freeing cache
Date: Thu, 23 Jun 2011 16:09:02 -0400 [thread overview]
Message-ID: <20110623200902.GC21007@dhcp231-156.rdu.redhat.com> (raw)
In-Reply-To: <1308858697-24067-1-git-send-email-josef@redhat.com>
On Thu, Jun 23, 2011 at 03:51:37PM -0400, Josef Bacik wrote:
> A user reported this bug again where we have more bitmaps than we are supposed
> to. This is because we failed to load the free space cache, but don't update
> the ctl->total_bitmaps counter when we remove entries from the tree. This patch
> fixes this problem and we should be good to go again. Thanks,
>
> Signed-off-by: Josef Bacik <josef@redhat.com>
> ---
> fs/btrfs/free-space-cache.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/fs/btrfs/free-space-cache.c b/fs/btrfs/free-space-cache.c
> index 3c1a047..aa62448 100644
> --- a/fs/btrfs/free-space-cache.c
> +++ b/fs/btrfs/free-space-cache.c
> @@ -1844,6 +1844,8 @@ void __btrfs_remove_free_space_cache_locked(struct btrfs_free_space_ctl *ctl)
> info = rb_entry(node, struct btrfs_free_space, offset_index);
> unlink_free_space(ctl, info);
> kfree(info->bitmap);
> + ctl->total_bitmaps--;
> + ctl->op->recalc_thresholds(ctl);
> kmem_cache_free(btrfs_free_space_cachep, info);
> if (need_resched()) {
> spin_unlock(&ctl->tree_lock);
> --
> 1.7.2.3
>
IGNORE THIS ONE. Sorry, this is what haste gets you.
Josef
prev parent reply other threads:[~2011-06-23 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 19:51 [PATCH] Btrfs: make sure to update total_bitmaps when freeing cache Josef Bacik
2011-06-23 20:09 ` Josef Bacik [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110623200902.GC21007@dhcp231-156.rdu.redhat.com \
--to=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox