From: Chris Mason <chris.mason@oracle.com>
To: Liu Bo <liubo2009@cn.fujitsu.com>, David Sterba <dsterba@suse.cz>,
linux-btrfs@vger.kernel.org, stable@vger.kernel.org,
Josef Bacik <josef@redhat.com>
Subject: Re: [PATCH] Revert "Btrfs: increase the global block reserve estimates"
Date: Tue, 10 Apr 2012 11:24:15 -0400 [thread overview]
Message-ID: <20120410152415.GW29506@shiny> (raw)
In-Reply-To: <20120409224008.GB11041@twin.jikos.cz>
On Tue, Apr 10, 2012 at 12:40:08AM +0200, David Sterba wrote:
> On Mon, Apr 09, 2012 at 09:37:08AM +0800, Liu Bo wrote:
> > The whole thing is about our overcommit stuff, that is,
> > since we are not able to get _precise_ number of reservation right now, we usually
> > reserve more than what we need.
> > For this, we've done overcommit dance (thanks for Josef's work!) but it's still not
> > enough for our reservation when we still have some disk space.
> >
> > I'm ok with this revert, but since we don't use up all the reserved space in most time,
> > I assume the following can be an alternative, thanks,
>
> Unfortunatelly the situation looks not good for 3.3 btrfs users, I'm
> looking for something we know that somehow (ie like in 3.2) works and
> are able to submit to the stable tree very soon. I'll definitelly test
> your alternative and if Chris applies it during the -rc phase we'll have
> more time to verify it or you/Josef fix it in another way.
Lets do the alternative of reverting the patch and dropping the warning.
I've been trying to find a small and simple patch for that but I don't
think that's going to happen for a stable commit.
-chris
next prev parent reply other threads:[~2012-04-10 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-08 23:40 [PATCH] Revert "Btrfs: increase the global block reserve estimates" David Sterba
2012-04-09 1:37 ` Liu Bo
2012-04-09 22:40 ` David Sterba
2012-04-10 15:24 ` Chris Mason [this message]
2012-04-11 16:00 ` David Sterba
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=20120410152415.GW29506@shiny \
--to=chris.mason@oracle.com \
--cc=dsterba@suse.cz \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).