From: Gabriel <g2p.code@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Poor performance of btrfs. Suspected unidentified btrfs housekeeping process which writes a lot
Date: Thu, 31 Jan 2013 19:06:17 +0000 (UTC) [thread overview]
Message-ID: <keefb9$unr$1@ger.gmane.org> (raw)
In-Reply-To: 510A3D1D.4010501@statystyka.net
Hi,
> After mounting the system with noatime the problem disappeared, like in
> magic.
Incidentally, the current version of bedup uses a private mountpoint with
noatime whenever you don't give it the path to a mounted volume. You can
use it with no arguments or designate a filesystem by its uuid or /dev
path.
> All the writes must have came from the dealyed metadata copy process.
> Once all the metadata copy-update was done, file system speed was back
> to normal, but once the new day broke out, all the copying business
> needed to done again... This in 100% describes all the odd behavior.
>
> In particular apparently the problem had nothing to do with my complex
> block device setup, nor with bedup, nor with unison.
>
> Thank you again, Andrew!
>
> P.S. Maybe it is not be decided by me, but this small message about
> performance (not even labeled as warning) in
> https://btrfs.wiki.kernel.org/index.php/Mount_options IMHO should have
> been made more conspicuous, maybe put somewhere when the snapshot
> mechanism is described or in FAQ. I'll try to fix it.
next prev parent reply other threads:[~2013-01-31 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAuLxcbVXFjzvZ+Oj4MUEHnsOhhbVPTeKx-34En2ym37J2wuuA@mail.gmail.com>
2013-01-31 9:45 ` Poor performance of btrfs. Suspected unidentified btrfs housekeeping process which writes a lot Adam Ryczkowski
2013-01-31 19:06 ` Gabriel [this message]
2013-01-30 14:57 Adam Ryczkowski
2013-01-30 23:58 ` Chris Murphy
2013-01-31 1:02 ` Adam Ryczkowski
2013-01-31 1:50 ` Chris Murphy
2013-01-31 10:56 ` Adam Ryczkowski
2013-01-31 19:08 ` Chris Murphy
2013-01-31 19:17 ` Adam Ryczkowski
2013-01-31 20:35 ` Chris Murphy
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='keefb9$unr$1@ger.gmane.org' \
--to=g2p.code@gmail.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 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.