From: Chris Mason <chris.mason@oracle.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Josef Bacik <jbacik@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: Hang running fs_mark
Date: Mon, 29 Sep 2008 14:48:49 -0400 [thread overview]
Message-ID: <1222714129.30627.27.camel@think.oraclecorp.com> (raw)
In-Reply-To: <48DC3455.9010907@redhat.com>
On Thu, 2008-09-25 at 21:01 -0400, Ric Wheeler wrote:
> Chris Mason wrote:
> > On Thu, 2008-09-25 at 18:58 -0400, Ric Wheeler wrote:
> >
> >>> I'm at 6.9 million files so far on a 500GB disk, and not surprisingly, I
> >>> get 155 files/sec ;) My hope is that we're spinning around due to bad
> >>> accounting on the reserved extents, and that Yan's latest patch set will
> >>> fix it.
> >>>
> >>> -chris
> >>>
> >> I can update & restart my test as well. It is an odd box (8 CPUs, only
> >> 1GB of DRAM and a single large 1TB s-ata drive). Hopefully useful in
> >> testing out edge conditions ;-)
> >>
> >
> > I'll push out Yan's patches tomorrow. My box here is at 17.5 million
> > files and still going at 148 files/sec
> >
> Sounds like a plan, thanks!
I turned up a long standing balancing bug while testing Yan's latest
code. It took forever to track down, but I've finally pushed out his
patches.
My fs_mark run never did stall, but I'm retesting now with all of the
latest changes. You'll need to pull the latest unstable btrfs-progs and
kernel from git.
-chris
next prev parent reply other threads:[~2008-09-29 18:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 17:56 Hang running fs_mark Josef Bacik
2008-09-25 18:37 ` Chris Mason
2008-09-25 18:34 ` Josef Bacik
2008-09-25 19:05 ` Chris Mason
2008-09-25 20:37 ` Ric Wheeler
2008-09-25 21:04 ` Chris Mason
2008-09-25 21:10 ` Ric Wheeler
2008-09-25 22:28 ` Chris Mason
2008-09-25 22:58 ` Ric Wheeler
2008-09-26 0:48 ` Chris Mason
2008-09-26 1:01 ` Ric Wheeler
2008-09-26 14:15 ` Chris Mason
2008-09-29 18:48 ` Chris Mason [this message]
2008-09-25 20:11 ` Ric Wheeler
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=1222714129.30627.27.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=jbacik@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rwheeler@redhat.com \
/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