From: "André-Sebastian Liebe" <andre@lianse.eu>
To: Chris Murphy <lists@colorremedies.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: [solved] Re: btrfs filesystem resize <ID>:max not working
Date: Fri, 10 Apr 2015 09:17:10 +0200 [thread overview]
Message-ID: <552778F6.8040604@lianse.eu> (raw)
In-Reply-To: <CAJCQCtS24gzNgOuUgea5_eT-7UDP4fDNMGAxfR5fcy6btK2FQw@mail.gmail.com>
Hey all,
On 04/09/2015 09:49 PM, Chris Murphy wrote:
> On Thu, Apr 9, 2015 at 10:03 AM, André-Sebastian Liebe <andre@lianse.eu> wrote:
>> 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.
> You did device add, device delete, then fi resize? It should work but
> it's better to use btrfs replace start for this sort of operation
> since it does all of that in one step.
I did a device replace.
>> 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?
> Not sure, this has always worked for me in the past, online. You could
> try unmounting and doing a btrfs dev scan, remounting, and then
> retrying the command. There's nothing in dmesg? There should be
> something there whether it succeeds or fails.
Okay, I did a scrub, unmounted it, scanned for devices, remounted it and
redid the resize for drive 4. This time I got a syslog entry showing the
start of the resize and about 5 minutes later the command finished
without an error.
Konsole output
> Apr 10 08:58:39 apc01 kernel: BTRFS info (device sdd): resizing devid 4
> Apr 10 08:58:39 apc01 kernel: BTRFS: new size for /dev/sdg is
6001175126016
`btrfs fi sh` finally shows both of my 6TB drives
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.60TiB path /dev/sdc
> devid 3 size 3.64TiB used 3.60TiB path /dev/sde
> devid 4 size 5.46TiB used 3.60TiB 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
Thanks for the hint!
Cheers
André
prev parent reply other threads:[~2015-04-10 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 16:03 btrfs filesystem resize <ID>:max not working André-Sebastian Liebe
2015-04-09 19:49 ` Chris Murphy
2015-04-10 7:17 ` André-Sebastian Liebe [this message]
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=552778F6.8040604@lianse.eu \
--to=andre@lianse.eu \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).