From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: 6+ MiB/s constant usage on a btrfs volume with kernel 3.16
Date: Sun, 24 Aug 2014 18:08:12 +0000 (UTC) [thread overview]
Message-ID: <pan.2014.08.24.18.08.12@googlemail.com> (raw)
In-Reply-To: 441201408902401@web23m.yandex.ru
On Sun, 24 Aug 2014 19:46:41 +0200, Flash ROM wrote:
>> Happens a 100% of the time here, annoyingly. As mentioned, 3.15 was
>> working for me, and still does. Multiple reboots and it happens
>> immediately on boot even before gdm comes up.
> Would be logical to do block-level I/O tracing to get idea WHAT is this
> IO, right?
Or you could just use proper tools for this:
iotop:
http://guichaz.free.fr/iotop/
iosnoop:
http://www.brendangregg.com/blog/2014-07-16/iosnoop-for-linux.html
Probably either a continuing balance or autodefrag vs. systemd's logging.
-h
next prev parent reply other threads:[~2014-08-24 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 9:55 6+ MiB/s constant usage on a btrfs volume with kernel 3.16 Oon-Ee Ng
2014-08-24 12:57 ` Duncan
2014-08-24 15:58 ` Oon-Ee Ng
2014-08-24 17:46 ` Flash ROM
2014-08-24 18:08 ` Holger Hoffstätte [this message]
2014-08-25 0:05 ` Oon-Ee Ng
2014-08-25 2:09 ` Oon-Ee Ng
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=pan.2014.08.24.18.08.12@googlemail.com \
--to=holger.hoffstaette@googlemail.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.