From: Hans-Kristian Bakke <hkbakke@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Non-intelligent behaviour on device delete with multiple devices?
Date: Sun, 27 Oct 2013 18:33:47 +0100 [thread overview]
Message-ID: <CAD_cGvGG9KPastZr1QCE_d0rmR=saj9Drj25hAzSzRkg6oEL2g@mail.gmail.com> (raw)
Hi
Today I tried removing two devices from a multidevice btrfs RAID10
volume using the following command:
---
btrfs device delete /dev/sdl /dev/sdk /btrfs
---
It first removed device sdl and then sdk. What I did not expect
however was that btrfs didn't remove sdk from the available drives
when removing and rebalancing data from the first device. This
resultated in that over 300GB of data was actually added to sdk during
removal of sdl, only to make the removal process of sdk longer.
This seems to me as a rather non-intelligent way to do this. I would
expect that all drives given as input to the btrfs device delete
command was removed from the list of drives available for rebalancing
of the data during removal of the drives.
Regards,
Hans-Kristian Bakke
next reply other threads:[~2013-10-27 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 17:33 Hans-Kristian Bakke [this message]
2013-10-27 21:16 ` Non-intelligent behaviour on device delete with multiple devices? Brendan Hide
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='CAD_cGvGG9KPastZr1QCE_d0rmR=saj9Drj25hAzSzRkg6oEL2g@mail.gmail.com' \
--to=hkbakke@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).