From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Adam Borowski <kilobyte@angband.pl>,
Juergen Sauer <juergen.sauer@automatix.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS Raid 5 Space missing - ideas ?
Date: Sun, 21 Apr 2019 07:39:59 +0300 [thread overview]
Message-ID: <02b7c96d-8ac6-ec2d-e2b8-8fa46d4e310b@gmail.com> (raw)
In-Reply-To: <20190420201913.GA3306@angband.pl>
20.04.2019 23:19, Adam Borowski пишет:
> On Sat, Apr 20, 2019 at 12:46:16PM +0200, Juergen Sauer wrote:
>> I wish a happy Easer Days before :)
>
> Same to you!
>
>> During my tests with BTRFS as Raid5 setup, I found a courious little
>> "problem".
>
>> Total devices 3 FS bytes used 9.98TiB
>> devid 1 size 9.09TiB used 4.99TiB path /dev/sdb1
>> devid 2 size 5.46TiB used 4.99TiB path /dev/sdc1
>> devid 3 size 5.46TiB used 4.99TiB path /dev/sde1
>
>> All patitioins sdb1 sdc1 sde1 are the same size: 9.0 TiB. But BTRFS ist
>> not using the bigger space on sdc1, sde1, there is only 5.46 TiB used,
>> even there are 9.0 Tib Avaible, so 4.0 TiB are unused.
>
> It's working as expected: while btrfs does RAID per block group rather than
> per whole block device, there's no way to place a raid5 block group in a way
> that doesn't require at least 3 devices. This means with a 3-disk setup the
> space utilized will be only as big as the smallest one.
>
But as reported, all drives were replaced by larger ones but only one
drive shows increased size: "All patitioins sdb1 sdc1 sde1 are the same
size".
next prev parent reply other threads:[~2019-04-21 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 10:46 BTRFS Raid 5 Space missing - ideas ? Juergen Sauer
2019-04-20 20:19 ` Adam Borowski
2019-04-21 4:39 ` Andrei Borzenkov [this message]
2019-04-21 6:50 ` [solved] " Juergen Sauer
2019-04-22 0:05 ` Zygo Blaxell
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=02b7c96d-8ac6-ec2d-e2b8-8fa46d4e310b@gmail.com \
--to=arvidjaar@gmail.com \
--cc=juergen.sauer@automatix.de \
--cc=kilobyte@angband.pl \
--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