From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-transacti hammering the system
Date: Mon, 4 Dec 2017 14:10:05 +0000 (UTC) [thread overview]
Message-ID: <pan$72fcb$25444603$d7f3231e$e556c8d5@cox.net> (raw)
In-Reply-To: 96e81cad-1024-aa9e-c3fe-d884a710b130@gmail.com
Austin S. Hemmelgarn posted on Mon, 04 Dec 2017 07:18:11 -0500 as
excerpted:
> 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.
Thanks. I wasn't aware global reserve was routinely temporarily used.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-12-04 14:10 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
2017-12-04 14:10 ` Duncan [this message]
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='pan$72fcb$25444603$d7f3231e$e556c8d5@cox.net' \
--to=1i5t5.duncan@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).