From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Nikolay Borisov <n.borisov.lkml@gmail.com>,
James Courtier-Dutton <james.dutton@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs balance problems
Date: Sat, 30 Dec 2017 01:43:24 +0100 [thread overview]
Message-ID: <82257976-5c34-45d1-d88f-fa12a66d24f4@mendix.com> (raw)
In-Reply-To: <e3629f7d-3278-bb11-d416-43e290c67e2a@gmail.com>
On 12/28/2017 12:15 PM, Nikolay Borisov wrote:
>
> On 23.12.2017 13:19, James Courtier-Dutton wrote:
>>
>> During a btrfs balance, the process hogs all CPU.
>> Or, to be exact, any other program that wishes to use the SSD during a
>> btrfs balance is blocked for long periods. Long periods being more
>> than 5 seconds.
>> Is there any way to multiplex SSD access while btrfs balance is
>> operating, so that other applications can still access the SSD with
>> relatively low latency?
>>
>> My guess is that btrfs is doing a transaction with a large number of
>> SSD blocks at a time, and thus blocking other applications.
>>
>> This makes for atrocious user interactivity as well as applications
>> failing because they cannot access the disk in a relatively low latent
>> manner.
>> For, example, this is causing a High Definition network CCTV
>> application to fail.
>>
>> What I would really like, is for some way to limit SSD bandwidths to
>> applications.
>> For example the CCTV app always gets the bandwidth it needs, and all
>> other applications can still access the SSD, but are rate limited.
>> This would fix my particular problem.
>> We have rate limiting for network applications, why not disk access also?
>
> So how are you running btrfs balance?
Or, to again take one step further back...
*Why* are you running btrfs balance at all?
:)
> Are you using any filters
> whatsoever? The documentation
> [https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-balance] has the
> following warning:
>
> Warning: running balance without filters will take a lot of time as it
> basically rewrites the entire filesystem and needs to update all block
> pointers.
--
Hans van Kranenburg
prev parent reply other threads:[~2017-12-30 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 11:19 btrfs balance problems James Courtier-Dutton
2017-12-23 11:56 ` Alberto Bursi
[not found] ` <CAAMvbhHV=BvRLv14U0JRrYmhiXeREOTNiVLPkuq=MO6dH4jDiQ@mail.gmail.com>
2017-12-27 21:39 ` James Courtier-Dutton
2017-12-27 21:54 ` waxhead
2017-12-28 0:39 ` Duncan
2017-12-30 0:34 ` Kai Krakow
2018-01-06 18:09 ` James Courtier-Dutton
2017-12-28 11:15 ` Nikolay Borisov
2017-12-30 0:43 ` Hans van Kranenburg [this message]
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=82257976-5c34-45d1-d88f-fa12a66d24f4@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=james.dutton@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=n.borisov.lkml@gmail.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;
as well as URLs for NNTP newsgroup(s).