Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Dmitrii Tcvetkov <demfloro@demfloro.ru>, FLJ <feci2048@gmail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: Help me understand what is going on with my RAID1 FS
Date: Sun, 10 Sep 2017 22:17:26 +0300	[thread overview]
Message-ID: <bae7bedb-4f3a-3779-e6c7-9d3879cb1d27@gmail.com> (raw)
In-Reply-To: <1F3219B0-72B2-4201-8C96-E6FBFD02A413@demfloro.ru>

10.09.2017 19:11, Dmitrii Tcvetkov пишет:
>> Actually based on http://carfax.org.uk/btrfs-usage/index.html I
>> would've expected 6 TB of usable space. Here I get 6.4 which is odd,
>> but that only 1.5 TB is available is even stranger.
>>
>> Could anyone explain what I did wrong or why my expectations are wrong?
>>
>> Thank you in advance
> 
> I'd say df and the website calculate different things. In btrfs raid1 profile stores exactly 2 copies of data, each copy is on separate device. 
> So by adding third drive, no matter how big, effective free space didn't expand because btrfs still needs space on any one of other two drives to store second half of each raid1 chunk stored on that third drive. 
> 
> Basically:
> 
> Drive1      Drive2    Drive3
> X           X
> X                         X
>             X             X
> 
> Where X is a chunk of raid1 block group.

But this table clearly shows that adding third drive increases free
space by 50%. You need to reallocate data to actually make use of it,
but it was done in this case.

  reply	other threads:[~2017-09-10 19:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-10 13:45 Help me understand what is going on with my RAID1 FS FLJ
2017-09-10 15:47 ` Kai Krakow
2017-09-10 16:50   ` Ferenc-Levente Juhos
2017-09-10 17:19     ` Dmitrii Tcvetkov
2017-09-10 18:15       ` Ferenc-Levente Juhos
2017-09-10 22:04         ` Kai Krakow
2017-09-10 19:14   ` Andrei Borzenkov
2017-09-10 16:11 ` Dmitrii Tcvetkov
2017-09-10 19:17   ` Andrei Borzenkov [this message]
2017-09-10 20:17     ` Dmitrii Tcvetkov
2017-09-11  3:29       ` Andrei Borzenkov
2017-09-11  8:18         ` FLJ
2017-09-11  0:12 ` Duncan

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=bae7bedb-4f3a-3779-e6c7-9d3879cb1d27@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=demfloro@demfloro.ru \
    --cc=feci2048@gmail.com \
    --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