From: Karsten Vinding <karstenvinding@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Balance of Raid1 pool, does not balance properly.
Date: Wed, 9 Jan 2019 18:20:55 +0100 [thread overview]
Message-ID: <64cf0762-bd59-3d77-8aca-94622233767f@gmail.com> (raw)
In-Reply-To: <cbffc26e-a57f-e1ad-284c-a54431c4e2f1@gmail.com>
Just a short answer.
I didn't use the replace command.
I added the new drive to the pool / array, and checked that it was
registered.
Following that I removed the 1TB drive with "btrfs device delete <drive>".
As far as I know this should avoid the need to resize the new drive.
"btrfs fi us" shows all the space as available. The drive shows 1.7TB as
unallocated.
I have started moving some data of the array to give btrfs some more
room to move, and will follow what happens when I try a new balance
later on.
next prev parent reply other threads:[~2019-01-09 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 19:40 Balance of Raid1 pool, does not balance properly Karsten Vinding
2019-01-09 1:08 ` Duncan
2019-01-09 17:20 ` Karsten Vinding [this message]
2019-01-09 20:47 ` Peter Becker
2019-01-10 18:21 ` Karsten Vinding
2019-01-10 18:58 ` Peter Becker
2019-01-11 22:04 ` Karsten Vinding
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=64cf0762-bd59-3d77-8aca-94622233767f@gmail.com \
--to=karstenvinding@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;
as well as URLs for NNTP newsgroup(s).