Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Tomas Carnecky <tom@dbservice.com>
To: linux-btrfs@vger.kernel.org
Subject: fixing slow sync(2)
Date: Sat, 08 Oct 2011 17:24:15 +0200	[thread overview]
Message-ID: <4E906B1F.6010609@dbservice.com> (raw)

The issue with sync(2) being slow has been known for a while now (I can 
find discussions as early as July 2010). But nobody seems to be willing 
to fix it or even figure out out what the actual problem is. I use btrfs 
on two hosts, and the sync(2) syscall is consistently slow. By slow I 
mean 20 seconds on one and 45(!) seconds on the other. Every single 
time, no exceptions.

Is there anything I can do to help track down the cause? I can test 
patches, trace the kernel or use whatever tool is most helpful.

tom

             reply	other threads:[~2011-10-08 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 15:24 Tomas Carnecky [this message]
2011-10-08 15:35 ` fixing slow sync(2) Josef Bacik
     [not found]   ` <CAE=-PDhvddavk9DyyF07gi0uq=a+WfGbXN89r28SRK9SYPaZfA@mail.gmail.com>
2011-10-11  3:11     ` John
2011-10-11 13:38     ` Josef Bacik
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=4E906B1F.6010609@dbservice.com \
    --to=tom@dbservice.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