From: Juergen Sauer <juergen.sauer@automatix.de>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-btrfs@vger.kernel.org
Subject: [solved] Re: BTRFS Raid 5 Space missing - ideas ?
Date: Sun, 21 Apr 2019 08:50:17 +0200 [thread overview]
Message-ID: <6643e50c-b7d4-6b85-97d8-e9cf76d4ebd2@automatix.de> (raw)
In-Reply-To: <02b7c96d-8ac6-ec2d-e2b8-8fa46d4e310b@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
Am 21.04.19 um 06:39 schrieb Andrei Borzenkov:
> 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
Mr. Bethencourt send me this night the helping hint.
I overread the updated syntax in the resize command.
The "btrfs filesystem resize" takes by default and silently the first
device to work on, no hint is issued.
It is mandatory to define the devid to work on for "resize" on multi
device btrfs volumes.
btrfs filesystem resize 2:max /srv
btrfs filesystem resize 3:max /srv
Made the wanted job as expected.
This is the result:
[root@pc6 ~]# btrfs filesystem show /srv
Label: 'Archiv' uuid: 662c9f40-56b0-4e4e-aa64-55039ff8f4f8
Total devices 3 FS bytes used 9.98TiB
devid 1 size 9.09TiB used 4.99TiB path /dev/sdb1
devid 2 size 9.09TiB used 4.99TiB path /dev/sdc1
devid 3 size 9.09TiB used 4.99TiB path /dev/sde1
root@pc6 ~]# df -h /srv
/dev/sdb1 28T 10T 13T 45% /srv
Thank you, Mr. Bethencourt and @all
mit freundlichen Grüßen
Jürgen Sauer
[-- Attachment #2: juergen_sauer.vcf --]
[-- Type: text/x-vcard, Size: 389 bytes --]
begin:vcard
fn;quoted-printable:J=C3=BCrgen Sauer
n;quoted-printable:Sauer;J=C3=BCrgen
org:automatiX GmbH
adr:;;Neue Str. 11;Schwanewede;Niedersachsen;28790;Deutschland
email;internet:juergen.sauer@automatix.de
tel;work:+49 4209 4699
tel;fax:+49 4209 4644
tel;home:+49 4209 4653
tel;cell:+49 162 9699 259
x-mozilla-html:FALSE
url:https://automatix.de
version:2.1
end:vcard
next prev parent reply other threads:[~2019-04-21 6:50 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
2019-04-21 6:50 ` Juergen Sauer [this message]
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=6643e50c-b7d4-6b85-97d8-e9cf76d4ebd2@automatix.de \
--to=juergen.sauer@automatix.de \
--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