From: Dave Chinner <david@fromorbit.com>
To: Chris Mason <chris.mason@oracle.com>,
Chris Samuel <chris@csamuel.org>,
linux-btrfs@vger.kernel.org
Subject: Re: [3.2-rc7] slowdown, warning + oops creating lots of files
Date: Fri, 6 Jan 2012 07:12:16 +1100 [thread overview]
Message-ID: <20120105201216.GG24466@dastard> (raw)
In-Reply-To: <20120105194500.GD30372@shiny>
On Thu, Jan 05, 2012 at 02:45:00PM -0500, Chris Mason wrote:
> On Thu, Jan 05, 2012 at 01:46:57PM -0500, Chris Mason wrote:
> > On Thu, Jan 05, 2012 at 10:01:22AM +1100, Dave Chinner wrote:
> > > On Thu, Jan 05, 2012 at 09:23:52AM +1100, Chris Samuel wrote:
> > > > On 05/01/12 09:11, Dave Chinner wrote:
> > > >
> > > > > Looks to be reproducable.
> > > >
> > > > Does this happen with rc6 ?
> > >
> > > I haven't tried. All I'm doing is running some benchmarks to get
> > > numbers for a talk I'm giving about improvements in XFS metadata
> > > scalability, so I wanted to update my last set of numbers from
> > > 2.6.39.
> > >
> > > As it was, these benchmarks also failed on btrfs with oopsen and
> > > corruptions back in 2.6.39 time frame. e.g. same VM, same
> > > test, different crashes, similar slowdowns as reported here:
> > > http://comments.gmane.org/gmane.comp.file-systems.btrfs/11062
> > >
> > > Given that there is now a history of this simple test uncovering
> > > problems, perhaps this is a test that should be run more regularly
> > > by btrfs developers?
> >
> > Unfortunately, this one works for me. I'll try it again and see if I
> > can push harder. If not, I'll see if I can trade beer for some
> > diagnostic runs.
>
> Aha, if I try it just on the ssd instead of on my full array it triggers
> at 88M files. Great.
Good to know. The error that is generating the BUG on my machine is
-28 (ENOSPC). Given there's 17TB free on my filesystem....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2012-01-05 20:12 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 [this message]
2012-01-05 21:02 ` Chris Mason
2012-01-05 21:24 ` Chris Samuel
2012-01-06 1:22 ` Chris Mason
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=20120105201216.GG24466@dastard \
--to=david@fromorbit.com \
--cc=chris.mason@oracle.com \
--cc=chris@csamuel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.