From: Josef Bacik <josef@redhat.com>
To: John <jello@waste.org>
Cc: Josef Bacik <josef@redhat.com>,
Tomas Carnecky <tom@dbservice.com>,
linux-btrfs@vger.kernel.org
Subject: Re: fixing slow sync(2)
Date: Tue, 11 Oct 2011 09:38:35 -0400 [thread overview]
Message-ID: <20111011133834.GA2293@localhost.localdomain> (raw)
In-Reply-To: <CAE=-PDhvddavk9DyyF07gi0uq=a+WfGbXN89r28SRK9SYPaZfA@mail.gmail.com>
On Mon, Oct 10, 2011 at 09:34:12PM -0500, John wrote:
> On Sat, Oct 8, 2011 at 10:35 AM, Josef Bacik <josef@redhat.com> wrote:
>
> >
> > I think I fixed this, try my git tree
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-work.git
> >
> > Let me know if it helps. And what are you doing when you call sync? I've
> > not
> > been able to reproduce this problem so I'm having a hard time nailing down
> > what
> > it is, so if I can get a reliable way to reproduce it I'll try and figure
> > it
> > out. Thanks,
> >
>
> I've been seeing very slow syncs (and unmounts) and this helps. Under 3.0.0
> if I mounted the FS (which is 200G, about 97G used with ~720 snapshots) it
> took about 3 minutes 40 seconds. If I did another sync right away it took
> the same amount of time. With a kernel compiled from your repo the first
> time I sync it takes about 1 minute, as soon as I sync a btrfs-endio-met
> and btrfs-cache-0 process show up in top and a lot of IO happens. Once those
> go away (which takes a couple minutes) then it takes well under a second. If
> I unmount and remount it acts exactly the same. Will those changes be up in
> 3.1 or 3.2? If you want me to test anything else, I'm happy to do so.
>
They'll show up in 3.2. Thanks for testing,
Josef
next prev parent reply other threads:[~2011-10-11 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 15:24 fixing slow sync(2) Tomas Carnecky
2011-10-08 15:35 ` Josef Bacik
[not found] ` <CAE=-PDhvddavk9DyyF07gi0uq=a+WfGbXN89r28SRK9SYPaZfA@mail.gmail.com>
2011-10-11 3:11 ` John
2011-10-11 13:38 ` Josef Bacik [this message]
2011-10-12 18:36 ` Dan Merillat
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=20111011133834.GA2293@localhost.localdomain \
--to=josef@redhat.com \
--cc=jello@waste.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=tom@dbservice.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