From: "André-Sebastian Liebe" <andre@lianse.eu>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: btrfs filesystem resize <ID>:max not working
Date: Thu, 09 Apr 2015 18:03:28 +0200 [thread overview]
Message-ID: <5526A2D0.2030103@lianse.eu> (raw)
Hey list,
I've got a problem with resizing a multi drive filesystem.
I had a 5 disk array of 4TB drives. Then I added a 5th (6TB) drive to
the array and replaced one of the 4TB ones with a 6TB drive. As you can
see in my `btrfs fi sh` output below, my newly added drive (ID=6) has
the expected size of 5.46TiB, but my replaced drive (ID=4) won't show up
as 6TB as expected. Neither a `btrfs fi res max /data/pool0` nor a
`btrfs fi res 4:max /data/pool0` had any effect.
Any suggestions how to reclaim the 2TB free space of drive 4?
Thanks in advance
André-Sebastian Liebe
> Kernel:Linux apc01 3.19.2-1-ARCH #1 SMP PREEMPT Wed Mar 18 16:21:02
CET 2015 x86_64 GNU/Linux
> btrfs-progs: btrfs-progs v3.19
My 6 drives used by the apc01_pool (none of them has a partition table)
Konsole output
> # hdparm -I /dev/sdb | grep "device size"
> device size with M = 1024*1024: 3815447 MBytes
> device size with M = 1000*1000: 4000787 MBytes (4000 GB)
> # hdparm -I /dev/sdc | grep "device size"
> device size with M = 1024*1024: 3815447 MBytes
> device size with M = 1000*1000: 4000787 MBytes (4000 GB)
> # hdparm -I /dev/sdd | grep "device size"
> device size with M = 1024*1024: 3815447 MBytes
> device size with M = 1000*1000: 4000787 MBytes (4000 GB)
> # hdparm -I /dev/sde | grep "device size"
> device size with M = 1024*1024: 3815447 MBytes
> device size with M = 1000*1000: 4000787 MBytes (4000 GB)
> # hdparm -I /dev/sdf | grep "device size"
> device size with M = 1024*1024: 5723166 MBytes
> device size with M = 1000*1000: 6001175 MBytes (6001 GB)
> # hdparm -I /dev/sdg | grep "device size"
> device size with M = 1024*1024: 5723166 MBytes
> device size with M = 1000*1000: 6001175 MBytes (6001 GB)
btrfs filesystem:
Konsole output
> # btrfs fi sh
> Label: 'apc01_pool0' uuid: 066141c6-16ca-4a30-b55c-e606b90ad0fb
> Total devices 6 FS bytes used 23.43TiB
> devid 1 size 3.64TiB used 3.61TiB path /dev/sdd
> devid 2 size 3.64TiB used 3.61TiB path /dev/sdc
> devid 3 size 3.64TiB used 3.61TiB path /dev/sde
> devid 4 size 3.64TiB used 3.61TiB path /dev/sdg
> devid 5 size 3.64TiB used 3.61TiB path /dev/sdb
> devid 6 size 5.46TiB used 5.43TiB path /dev/sdf
next reply other threads:[~2015-04-09 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 16:03 André-Sebastian Liebe [this message]
2015-04-09 19:49 ` btrfs filesystem resize <ID>:max not working Chris Murphy
2015-04-10 7:17 ` [solved] " André-Sebastian Liebe
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=5526A2D0.2030103@lianse.eu \
--to=andre@lianse.eu \
--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).