From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>,
"Matt McKinnon" <matt@techsquare.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs-transacti hammering the system
Date: Fri, 1 Dec 2017 19:24:07 +0100 [thread overview]
Message-ID: <b7294c64-280e-7415-6ae9-7673a37f7370@mendix.com> (raw)
In-Reply-To: <62d9e40d-3a73-303e-51d5-1b146230fa0d@applied-asynchrony.com>
On 12/01/2017 06:57 PM, Holger Hoffstätte wrote:
> On 12/01/17 18:34, Matt McKinnon wrote:
>> Thanks, I'll give space_cache=v2 a shot.
>
> Yes, very much recommended.
>
>> My mount options are: rw,relatime,space_cache,autodefrag,subvolid=5,subvol=/
>
> Turn autodefrag off and use noatime instead of relatime.
>
> Your filesystem also seems very full,
We don't know. btrfs fi df only displays allocated space. And that being
full is good, it means not too much free space fragments everywhere.
> that's bad with every filesystem but
> *especially* with btrfs because the allocator has to work really hard to find
> free space for COWing. Really consider deleting stuff or adding more space.
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-12-01 18:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 14:25 btrfs-transacti hammering the system Matt McKinnon
2017-12-01 14:52 ` Hans van Kranenburg
2017-12-01 15:24 ` Matt McKinnon
2017-12-01 15:39 ` Hans van Kranenburg
2017-12-01 15:42 ` Matt McKinnon
2017-12-01 16:31 ` Matt McKinnon
2017-12-01 17:06 ` Hans van Kranenburg
2017-12-01 17:13 ` Andrei Borzenkov
2017-12-01 18:04 ` Austin S. Hemmelgarn
2017-12-02 19:42 ` Andrei Borzenkov
2017-12-01 17:34 ` Matt McKinnon
2017-12-01 17:57 ` Holger Hoffstätte
2017-12-01 18:24 ` Hans van Kranenburg [this message]
2017-12-01 19:07 ` Matt McKinnon
2017-12-01 21:03 ` Chris Murphy
2017-12-01 21:47 ` Duncan
2017-12-01 21:50 ` Matt McKinnon
2017-12-04 12:18 ` Austin S. Hemmelgarn
2017-12-04 14:10 ` Duncan
2017-12-04 14:30 ` Austin S. Hemmelgarn
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=b7294c64-280e-7415-6ae9-7673a37f7370@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=holger@applied-asynchrony.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=matt@techsquare.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).