From: Chris Mason <chris.mason@oracle.com>
To: Chris Samuel <chris@csamuel.org>
Cc: Dave Chinner <david@fromorbit.com>, linux-btrfs@vger.kernel.org
Subject: Re: [3.2-rc7] slowdown, warning + oops creating lots of files
Date: Thu, 5 Jan 2012 20:22:44 -0500 [thread overview]
Message-ID: <20120106012244.GO30372@shiny> (raw)
In-Reply-To: <1325798672.17974.2.camel@Nokia-N900>
On Fri, Jan 06, 2012 at 08:24:32AM +1100, Chris Samuel wrote:
> On Fri,=A0 6 Jan 2012, 08:02:55 EST, Chris Mason <chris.mason@oracle=
=2Ecom> wrote:
>=20
> > Yeah, same thing here.=A0 I'm testing a fix now, it's pretty dumb.=
=A0 We're
> > not allocating more metadata chunks from the drive because of where=
the
> > allocation is happening, so it is just a check for "do we need a ne=
w
> > chunk" in the right place.
> >=20
> > I'll make sure it can fill my ssd and then send to you.
>=20
> *If* the fix works would this be a candidate for a
> stable 3.2.1 release rather than having to wait for
> 3.3?
Yes, it's pretty safe.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-06 1:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 21:44 [3.2-rc7] slowdown, warning + oops creating lots of files Dave Chinner
2012-01-04 22:11 ` Dave Chinner
2012-01-04 22:23 ` Chris Samuel
2012-01-04 23:01 ` Dave Chinner
2012-01-05 2:23 ` Liu Bo
2012-01-05 2:26 ` Dave Chinner
2012-01-05 19:11 ` Liu Bo
2012-01-05 11:43 ` Dave Chinner
2012-01-05 18:46 ` Chris Mason
2012-01-05 19:45 ` Chris Mason
2012-01-05 20:12 ` Dave Chinner
2012-01-05 21:02 ` Chris Mason
2012-01-05 21:24 ` Chris Samuel
2012-01-06 1:22 ` Chris Mason [this message]
2012-01-07 21:34 ` Christian Brunner
2012-01-12 16:18 ` Christian Brunner
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=20120106012244.GO30372@shiny \
--to=chris.mason@oracle.com \
--cc=chris@csamuel.org \
--cc=david@fromorbit.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;
as well as URLs for NNTP newsgroup(s).