From: Nikolay Borisov <nborisov@suse.com>
To: Wolf <wolf@wolfsden.cz>, linux-btrfs@vger.kernel.org
Subject: Re: Healthy amount of free space?
Date: Tue, 17 Jul 2018 10:20:49 +0300 [thread overview]
Message-ID: <1dd72720-1beb-a5e6-5bd4-88d6af5f02bd@suse.com> (raw)
In-Reply-To: <20180716205809.42jywfvuxwuuqixd@wolfsden.cz>
On 16.07.2018 23:58, Wolf wrote:
> Greetings,
> I would like to ask what what is healthy amount of free space to keep on
> each device for btrfs to be happy?
>
> This is how my disk array currently looks like
>
> [root@dennas ~]# btrfs fi usage /raid
> Overall:
> Device size: 29.11TiB
> Device allocated: 21.26TiB
> Device unallocated: 7.85TiB
> Device missing: 0.00B
> Used: 21.18TiB
> Free (estimated): 3.96TiB (min: 3.96TiB)
> Data ratio: 2.00
> Metadata ratio: 2.00
> Global reserve: 512.00MiB (used: 0.00B)
>
> Data,RAID1: Size:10.61TiB, Used:10.58TiB
> /dev/mapper/data1 1.75TiB
> /dev/mapper/data2 1.75TiB
> /dev/mapper/data3 856.00GiB
> /dev/mapper/data4 856.00GiB
> /dev/mapper/data5 1.75TiB
> /dev/mapper/data6 1.75TiB
> /dev/mapper/data7 6.29TiB
> /dev/mapper/data8 6.29TiB
>
> Metadata,RAID1: Size:15.00GiB, Used:13.00GiB
> /dev/mapper/data1 2.00GiB
> /dev/mapper/data2 3.00GiB
> /dev/mapper/data3 1.00GiB
> /dev/mapper/data4 1.00GiB
> /dev/mapper/data5 3.00GiB
> /dev/mapper/data6 1.00GiB
> /dev/mapper/data7 9.00GiB
> /dev/mapper/data8 10.00GiB
>
> System,RAID1: Size:64.00MiB, Used:1.50MiB
> /dev/mapper/data2 32.00MiB
> /dev/mapper/data6 32.00MiB
> /dev/mapper/data7 32.00MiB
> /dev/mapper/data8 32.00MiB
>
> Unallocated:
> /dev/mapper/data1 1004.52GiB
> /dev/mapper/data2 1004.49GiB
> /dev/mapper/data3 1006.01GiB
> /dev/mapper/data4 1006.01GiB
> /dev/mapper/data5 1004.52GiB
> /dev/mapper/data6 1004.49GiB
> /dev/mapper/data7 1005.00GiB
> /dev/mapper/data8 1005.00GiB
>
> Btrfs does quite good job of evenly using space on all devices. No, how
> low can I let that go? In other words, with how much space
> free/unallocated remaining space should I consider adding new disk?
Btrfs will start running into problems when you run out of unallocated
space. So the best advice will be monitor your device unallocated, once
it gets really low - like 2-3 gb I will suggest you run balance which
will try to free up unallocated space by rewriting data more compactly
into sparsely populated block groups. If after running balance you
haven't really freed any space then you should consider adding a new
drive and running balance to even out the spread of data/metadata.
>
> Thanks for advice :)
>
> W.
>
next prev parent reply other threads:[~2018-07-17 7:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 20:58 Healthy amount of free space? Wolf
2018-07-17 7:20 ` Nikolay Borisov [this message]
2018-07-17 8:02 ` Martin Steigerwald
2018-07-17 8:16 ` Nikolay Borisov
2018-07-17 17:54 ` Martin Steigerwald
2018-07-18 12:35 ` Austin S. Hemmelgarn
2018-07-18 13:07 ` Chris Murphy
2018-07-18 13:30 ` Austin S. Hemmelgarn
2018-07-18 17:04 ` Chris Murphy
2018-07-18 17:06 ` Austin S. Hemmelgarn
2018-07-18 17:14 ` Chris Murphy
2018-07-18 17:40 ` Chris Murphy
2018-07-18 18:01 ` Austin S. Hemmelgarn
2018-07-18 21:32 ` Chris Murphy
2018-07-18 21:47 ` Chris Murphy
2018-07-19 11:21 ` Austin S. Hemmelgarn
2018-07-20 5:01 ` Andrei Borzenkov
2018-07-20 11:36 ` Austin S. Hemmelgarn
2018-07-17 11:46 ` 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=1dd72720-1beb-a5e6-5bd4-88d6af5f02bd@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wolf@wolfsden.cz \
/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).