From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: linux-btrfs@vger.kernel.org
Subject: BTRFS and "ionice"
Date: Mon, 11 Mar 2013 11:26:41 +0100 [thread overview]
Message-ID: <513DB161.4050205@petaramesh.org> (raw)
Hi,
I use "ionice -c 3 <command>" to run some low-priority background tasks
(i.e. tar, big file copies, or performing checksums sur very big files)
using the disk "only when idle", which would be supposed to have very
little impact on my system performance meanwhile.
I can be pretty sure that those tasks are I/O-bound and use very little
CPU (and they are niced as well, anyway).
However, when such tasks are running my BTRFS system slows down to a
crawl, becomes very very unresponsive, and it seems to me that disk I/O
is completely saturated (LED is fixed lit...)
So I wonder if BTRFS correctly support ionice, or if it's plain useless ?
TIA
Kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
Ne cherchez pas : Je ne suis pas sur Facebook.
next reply other threads:[~2013-03-11 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 10:26 Swâmi Petaramesh [this message]
2013-03-11 12:52 ` BTRFS and "ionice" Dan van der Ster
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=513DB161.4050205@petaramesh.org \
--to=swami@petaramesh.org \
--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