From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Matt McKinnon <matt@techsquare.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-transacti hammering the system
Date: Mon, 4 Dec 2017 07:18:11 -0500 [thread overview]
Message-ID: <96e81cad-1024-aa9e-c3fe-d884a710b130@gmail.com> (raw)
In-Reply-To: <113cba02-2557-d1e8-193f-fab4437f1199@techsquare.com>
On 2017-12-01 16:50, Matt McKinnon wrote:
> Well, it's at zero now...
>
> # btrfs fi df /export/
> Data, single: total=30.45TiB, used=30.25TiB
> System, DUP: total=32.00MiB, used=3.62MiB
> Metadata, DUP: total=66.50GiB, used=65.16GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
GlobalReserve seems to be used temporarily for certain cases of metadata
COW regardless of how full the FS actually is, I'm betting that it just
so happened that such a case was in progress when you got the info
previously. If you aren't seeing it regularly used, it's (probably) not
an issue.
Duncan is correct though when dealing with long-term usage. If you see
GlobalReserve usage that persists for an extended period of time,
something is almost certainly wrong, especially if the FS isn't close to
being full.
>
>
> On 01/12/17 16:47, Duncan wrote:
>> Hans van Kranenburg posted on Fri, 01 Dec 2017 18:06:23 +0100 as
>> excerpted:
>>
>>> On 12/01/2017 05:31 PM, Matt McKinnon wrote:
>>>> Sorry, I missed your in-line reply:
>>>>
>>>>
>>>>> 2) How big is this filesystem? What does your `btrfs fi df
>>>>> /mountpoint` say?
>>>>>
>>>>
>>>> # btrfs fi df /export/
>>>> Data, single: total=30.45TiB, used=30.25TiB
>>>> System, DUP: total=32.00MiB, used=3.62MiB
>>>> Metadata, DUP: total=66.50GiB, used=65.08GiB
>>>> GlobalReserve, single: total=512.00MiB, used=53.69MiB
>>>
>>> Multi-TiB filesystem, check. total/used ratio looks healthy.
>>
>> Not so healthy, from here. Data/metadata are healthy, yes,
>> but...
>>
>> Any usage at all of global reserve is a red flag indicating that
>> something in the filesystem thinks, or thought when it resorted
>> to global reserve, that space is running out.
>>
>> Global reserve usage doesn't really hint what the problem is,
>> but it's definitely a red flag that there /is/ a problem, and
>> it's easily overlooked, as it apparently was here.
>>
>> It's likely indication of a bug, possibly one of the ones fixed
>> right around 4.12/4.13. I'll let the devs and better experts take
>> it from there, but I'd certainly be worried until global reserve
>> drops to zero usage.
>>
next prev parent reply other threads:[~2017-12-04 12:18 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
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 [this message]
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=96e81cad-1024-aa9e-c3fe-d884a710b130@gmail.com \
--to=ahferroin7@gmail.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).