From: Josef Bacik <josef@redhat.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: Josef Bacik <josef@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: allow us to overcommit our enospc reservations TEST THIS PLEASE!!!
Date: Tue, 11 Oct 2011 13:43:17 -0400 [thread overview]
Message-ID: <20111011174316.GE2293@localhost.localdomain> (raw)
In-Reply-To: <CAKcLGm_oFQOCCeFs69ohGfskkCj1FSbdxL18653ANoTX75n4SQ@mail.gmail.com>
On Tue, Oct 11, 2011 at 12:33:48PM -0500, Mitch Harder wrote:
> On Mon, Sep 26, 2011 at 4:22 PM, Josef Bacik <josef@redhat.com> wrote=
:
> >
> > go from taking around 45 minutes to 10 seconds on my freshly format=
ted 3 TiB
> > file system. =A0This doesn't seem to break my other enospc tests, b=
ut could really
> > use some more testing as this is a super scary change. =A0Thanks,
> >
>=20
> I've been testing Josef's git.kernel.org testing tree, and I've
> bisected an error down to this commit.
>=20
> I'm triggering the error using a removedirs benchmark in filebench
> with the following profile:
> load removedirs
> set $dir=3D/mnt/benchmark/filebench
> set $ndirs=3D400000
> run
>=20
Ouch. Does your pull have this patch
Btrfs: wait for ordered extents if we didn't reclaim enough
If not can you repull and retry your test? Thanks,
Josef
--
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:[~2011-10-11 17:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 21:22 [PATCH] Btrfs: allow us to overcommit our enospc reservations TEST THIS PLEASE!!! Josef Bacik
2011-10-11 17:33 ` Mitch Harder
2011-10-11 17:43 ` Josef Bacik [this message]
2011-10-11 18:27 ` Josef Bacik
2011-10-11 19:00 ` Josef Bacik
2011-10-11 19:44 ` Mitch Harder
2011-10-11 20:01 ` Josef Bacik
2011-10-11 20:45 ` Mitch Harder
2011-10-12 17:50 ` Josef Bacik
2011-10-12 20:45 ` Mitch Harder
2011-10-13 12:57 ` Josef Bacik
2011-10-13 15:03 ` 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=20111011174316.GE2293@localhost.localdomain \
--to=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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).